From: David Brower <dbrower@us.oracle.com>
To: linux-lvm@msede.com
Subject: [linux-lvm] current lvm function questions
Date: Tue, 26 Sep 2000 18:20:44 -0700 [thread overview]
Message-ID: <39D14B6C.4C9F6C26@us.oracle.com> (raw)
Hi, sorry to ask what might be FAQs, but I couldn't find
the answers on the list archive or the HOWTO. There may
be overlap in my interests between lvm and md, so please
straighten me out.
Area 1: Stable device naming.
Is there a way in Linux to get a stable name for a
disk that survive reconfiguration and discovery
randomization?
One of the things linux has problems with is
stable device naming. If you pull a disk out of a chain,
the following devices will move up in the /dev entries,
and not have the same name they had before. This can
be a real problem with massive storage subsystems.
I know of two ways of handling this. (1) is to slap
a label on the disk, and make sure it shows up as the
device in the label when the disk is discovered. (2)
is to keep a separate database mapping devices to fixed
locations. I think the label is the best idea.
It seems to me that lvm already slaps a label on the
disk when it does pvcreate. What i'm not sure of is
whether the label used is (a) globally unique and suitable
for stable device naming, or (b) tied to the device it
happened to be on at the time the pvcreate was issued.
Specifically, if a pv/vg/lv is created on /dev/sda6, and
a subsequent reconfig has that partition show up as
/dev/sdb3, does it still show up as /dev/lvname?
2. Raw device access
Can lvm volumes be accessed as raw devices? If so, how?
Is there /dev/rlvname?
I'm sure /dev/fs falls in here somewhere...
thanks!
-dB
next reply other threads:[~2000-09-27 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-27 1:20 David Brower [this message]
2000-09-27 2:24 ` [linux-lvm] current lvm function questions Eric Whiting
2000-09-27 10:28 ` Andi Kleen
2000-09-28 16:26 ` Christoph Hellwig
2000-09-28 16:32 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39D14B6C.4C9F6C26@us.oracle.com \
--to=dbrower@us.oracle.com \
--cc=linux-lvm@msede.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.