Table of Contents
Advertisement
7 If you want the volume group to only be activated exclusively on one node, use
the following example; in this case, cLVM will protect all logical volumes
within the VG from being activated on multiple nodes, as an additional measure
of protection for non-clustered applications:
primitive vg1 ocf:heartbeat:LVM \
params volgrpname="<volume group name>" exclusive="yes"
colocation colo-vg1 inf: vg1 clvm-clone
order order-vg1 inf: clvm-clone vg1
8 The logical volumes within the VG are now available as file system mounts or
raw usage. Ensure that services using them must have proper dependencies to
collocate them with and order them after the VG has been activated.
After finishing these configuration steps, the LVM2 configuration can be done just like
on any standalone workstation.
13.2 Configuring Eligible LVM2
Devices Explicitly
When several devices seemingly share the same physical volume signature (as can be
the case for multipath devices or drbd), it is recommended to explicitly configure the
devices which LVM2 scans for PVs.
For example, if the command vgcreate uses the physical device instead of using the
mirrored block device, DRBD will be confused which may result in a split brain condi-
tion for DRBD.
To deactivate a single device for LVM2, do the following:
1 Edit the file /etc/lvm/lvm.conf and search for the line starting with
filter.
2 The patterns there are handled as regular expressions. A leading "a" means to
accept a device pattern to the scan, a leading "r" rejects the devices that follow
the device pattern.
Cluster LVM
119
Advertisement
Table of Contents
Troubleshooting
