Les Mikesell wrote: >> >> It was an early design decision that every VG on a system should have a >> different name. Departures from that won't get supported - because >> it's so >> simple to choose different names! > How do you move drives around among machines then, if they have been > created with the default names that will conflict? SAN based snapshots are the legitimate reason to wish for multiple VGs with the same name. However, it is simpler all around if there was an easy way to relabel SAN snapshots before the duplicate names (and VGIDs) cause trouble. Apart from SAN snapshots, my rule of thumb is that local fixed drives are always called "rootvg". All removeable, SAN, or other drives that are likely to logically or physically move between machines get unique VG names. In the rare event I need to mount a rootvg from a failed machine on a working machine (has happened only once), I boot from CD to rename it (and the unique VGIDs make this doable).
begin:vcard fn:Stuart Gathman n:Gathman;Stuart org:Business Management Systems, Inc adr;dom:;;4001 Williamsburg Court;Fairfax;VA;22032 email;internet:stuart@bmsi.com tel;work:703 591-0911 tel;fax:703 591-6154 tel;home:703 378-9641 note:AIM: SDGathman x-mozilla-html:FALSE url:http://bmsi.com version:2.1 end:vcard
_______________________________________________ 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/
