On 5/4/15 9:11 AM, Pavelka, Tomas wrote:
People often give non-unique names to volume groups. For example if you name the VG root resides on "RootVG" and try to access it (via CP LINK) from another Linux system that also has root on "RootVG" then you can't put the VG online. We once got around this by using UUIDs for VGs, this ensures that any root FS is accessible from other Linuxes that can be used as emergency repair machines.
FWIW, I've setup two RHEL 6.x Linux systems on our mainframe. My installs were pretty much vanilla, with defaults for just about everything. The root file systems got defined on logical volumes, but I notice that the install process used the host name as part of the volume group name. On our zlinux1 host the VG name is "vg_zlinux1", on zlinux2 the VG name is "vg_zlinux2". We had some problems on the zlinux1 system a month or so ago that were causing fsck failures on the root file system. Because of that default naming convention, I shutdown zlinux1, logged the guest off VM and then had no problem mounting vg_zlinux1 on the zlinux2 host. Took a couple minutes to fsck the bad file system and then get zlinux1 running again. Personally, I like logical volumes!
Eric ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
