From: Andreas Dilger <adilger@turbolabs.com>
To: list LVM <linux-lvm@sistina.com>,
Igor Dumaire <Igor.Dumaire@LTUtech.com>
Subject: Re: [linux-lvm] Just for information ....
Date: Tue Nov 20 16:05:02 2001 [thread overview]
Message-ID: <20011120150638.E1308@lynx.no> (raw)
In-Reply-To: <20011120214104.A24005@cistron.nl>; from wichert@cistron.nl on Tue, Nov 20, 2001 at 09:41:04PM +0100
On Nov 20, 2001 21:41 +0100, Wichert Akkerman wrote:
> Previously Andreas Dilger wrote:
> > Yes. You will need to do a vgscan to find the new disks. Hopefully they
> > will not have the same VG name as another VG on that system.
>
> What if they do?
Then it will depend on disk ordering which one you get under that name, and
the other will be unavailable. vgscan will see all of the disks, but then
start checking the UUIDs on the PVs against the list on the "first" disk,
and the extra disks with UUIDs that don't match will be discarded.
I don't think there are any likely scenarios with LVM 0.9+ that will cause
problems, but since UUIDs were only introduced in 0.9, it may be much harder
to handle this in older LVM versions.
You might be able to vgexport the disks from the "other" VG at that time,
and reimport it with a different name, but I don't know how reliable that
will be (if it even works). LVM has been confused by less. Better to just
"not do that" in the first place.
FYI, AIX LVM does not keep the VG name on the disk itself, only a UUID.
You also never do something like "vgscan" at boot time to reconfigure
the LVM setup. When you attach the disks to a new system, you have to
import them (at which point they get a name that is stored in a config
file in /etc), and your LVM config is never touched until you change it.
When you export the VG, it also doesn't write to the disks, just deletes
the config from /etc. This means you don't need to do anything to the
VG before moving it to another system.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-20 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 12:39 [linux-lvm] Just for information Igor Dumaire
2001-11-20 13:55 ` Andreas Dilger
2001-11-20 14:39 ` Wichert Akkerman
2001-11-20 15:36 ` Chad C. Walstrom
2001-11-20 16:05 ` Andreas Dilger [this message]
2001-11-23 6:07 ` Heinz J . Mauelshagen
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=20011120150638.E1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=Igor.Dumaire@LTUtech.com \
--cc=linux-lvm@sistina.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