Linux LVM users
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@caldera.de>
To: David Brower <dbrower@us.oracle.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] current lvm function questions
Date: Thu, 28 Sep 2000 18:32:43 +0200	[thread overview]
Message-ID: <20000928183243.B14386@ns.lst.de> (raw)
In-Reply-To: <39D14B6C.4C9F6C26@us.oracle.com>; from dbrower@us.oracle.com on Tue, Sep 26, 2000 at 06:20:44PM -0700

On Tue, Sep 26, 2000 at 06:20:44PM -0700, David Brower wrote:
> 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?

There are lots ...

 a) use scsidev(2) (for scsi disks only)
 b) use devfs
 c) use the linux software raid driver
 d) use a hardware raid controller that has it's
    own devfs-like naming scheme (ami, compaq)
 e) use lvm - also it does not use UUIDs yet,
    vgscan should detect all pvs of a vg.
 f) mount you disk by-label instead of by-device
    (LABEL: or UUID: entries in /etc/fstab)

> 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?

It should. (but it's called /dev/vgname/lvname)

> 
> 2.  Raw device access
> 
> Can lvm volumes be accessed as raw devices?  If so, how?

Yes - in Linux 2.4 (or 2.2 w/ patches) you can simply bind
a raw device to any blockdevice. See raw(8) for details.
The device name will be /dev/raw/X

> Is there /dev/rlvname?

Nope.

	Christoph

-- 
Always remember that you are unique.  Just like everyone else.

      parent reply	other threads:[~2000-09-28 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-27  1:20 [linux-lvm] current lvm function questions David Brower
2000-09-27  2:24 ` Eric Whiting
2000-09-27 10:28 ` Andi Kleen
2000-09-28 16:26   ` Christoph Hellwig
2000-09-28 16:32 ` Christoph Hellwig [this message]

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=20000928183243.B14386@ns.lst.de \
    --to=hch@caldera.de \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox