All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Marxmeier <mike@msede.com>
To: EXT / DEVOTEAM VAROQUI Christophe <ext.devoteam.varoqui@sncf.fr>,
	linux-lvm@msede.com
Subject: [linux-lvm] Re: LVM+e2label
Date: Wed, 08 Mar 2000 03:21:04 +0100	[thread overview]
Message-ID: <38C5B910.8F32EF32@msede.com> (raw)
In-Reply-To: Pine.LNX.4.21.0003071349060.17755-100000@p64p17bia59.aigf.sncf.fr

EXT / DEVOTEAM VAROQUI Christophe (ext.devoteam.varoqui@sncf.fr)
wrote:
> The mount command is able to mount filesystems naming them by their
> label instead of their device-name :
> Thus, you're free to move your disks over different targets, hosts,
> even free to insert a new host in your pci chain (feature that
> devfs doesn't provide)
> 
> Question is :
> Are the lvm-tools able to create PV and VG naming partitions by
> label instead of device-names
> If not, is it planed to do so ?

You do not need it because LVM already should do this on its own.

vgscan scans all physical devices and creates its own map in
/etc/lvmtab. With LVM block devices have symbolic names 
(/dev/vg00/lvol1) and the physical devices are discovered/associated 
by their VGDA during vgscan. The physical address should not really 
matter.

I did not actually try this but it should work.

Michael

-- 
Michael Marxmeier           Marxmeier Software AG
E-Mail: mike@msede.com      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/

           reply	other threads:[~2000-03-08  2:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.21.0003071349060.17755-100000@p64p17bia59.aigf.sncf.fr>]

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=38C5B910.8F32EF32@msede.com \
    --to=mike@msede.com \
    --cc=ext.devoteam.varoqui@sncf.fr \
    --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.