Paul Howarth wrote:
On Mon, 2006-07-10 at 13:30 -0700, Tom Spec wrote:
Two systems using shared disks in a clustered environment.
When both systems are up I can de-activate the VG on one system,
activate it on the other and vice-versa. What I'm not sure about is
what happens if the "non-active" system reboots. Will it try to
activate those VGs (which are currently in use by the other system?)
Is this an issue?
Dunno; not done clusters. The "vgchange" manpage sounds promising with
its "l" and "e" options, but rc.sysinit looks worrying with
--ignorelockingfailure:
if [ -x /sbin/lvm.static ]; then
if /sbin/lvm.static vgscan --mknodes
--ignorelockingfailure > /dev/null 2>&1 ; then
action $"Setting up Logical Volume
Management:" /sbin/lvm.static vgchange -a y --ignorelockingfailure
fi
fi
The "vgscan" manpage looks to have something useful though:
vgscan scans all SCSI, (E)IDE disks, multiple devices and a bunch of
other disk devices in the system looking for LVM physical volumes and
volume groups. Define a filter in lvm.conf(8) to restrict the scan to
avoid a CD ROM, for example.
You could probably filter out your shared disks this way.
Paul.
You might want to pose this question to the LVM mail list at
linux-lvm@xxxxxxxxxx
