On 29 Mar 2007, Stuart D. Gathman said: > For anything that will never be physically moved to another machine, keep > it all on one volume group. But, for instance, if you think you might > want to move the iSCSI data to another box at some point, keep it > in its own VG (with its own set of drives) to make that easy. I also use VGs when I have several classes of PV with radically different properties (especially failure properties) and want to be sure that the failure of one PV can't possibly affect the LVs on the devices with other failure properties. At one point I had three VGs on one of my systems. One spanned PVs on top of a RAID-5 md array. That array was composed of disks of radically different sizes, so I had another VG spanning PVs consuming all that slack space. Then, for testing purposes, I had another VG sitting entirely atop the network block device. The NBDed VG could be expected to go down fairly frequently (as NBD connections don't outlast server reboots), but I didn't want that to affect either of the local VGs. The non-RAIDed VG might fail if a single disk dies, but that only had news spool and caches on it so I didn't want it to affect the important stuff on the RAIDed VGs. Hence, three VGs made considerable sense. _______________________________________________ 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/
