On Wed, 19 May 2010, Ray Morris wrote:
> It's also useful during the boot process. If, for example, you
> later add another disk, this disk might become sdd, where it used to
> be sdc. That can confuse initrd and friends and result in an
> unbootable system. On almost every machine where I've skipped
> creating partitions for RAID or LVM, this kind of thing has come
> back to bite me later - maybe years later. Now, I always create
> "Linux LVM" partitions for LVM and "Linux raid autodetect" partitions
> for RAID. It makes booting an recovering much more reliable in
> case of changes or problems.
PVs are identified by UUID. It doesn't matter whether they change
names. And changing names from sdc1 to sdd1 is just as bad as changing
names from sdc to sdd.
However, you are correct that the default device searching rules used by
lvm might work correctly with a Linux LVM labeled partition where they might
otherwise skip a device. If you aren't familiar with lvm.conf, then
using labeled partitions is a safer course. (initrd uses a copy
of lvm.conf to find PVs so it can activate the volume group of the
root filesystem if necessary.)
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
