+++ This bug was initially created as a clone of Bug #158231, and addresses
point 4 (2) of that bug's original message +++
Description of problem:
Rob Kenna, Jonathan Brassow, and Lon Hohberger put togather a RHEL 4 cluster/GFS
class on 5/18/05 with a hand-on lab exercise for GSS group. This bugzilla
documents one of the problems (on system-config-lvm) we found during the exercise.
Though most of them were trivial issues, these do represent the "look and feel"
of the product that real customers are going to see.
Editing of /etc/lvm/lvm.conf File
(severity low)(not a bug but a usability issue)
1 It is not clear (to us) that the /etc/lvm/lvm.conf file need to get edited
on *every* node in the same GFS cluster.
2 Jumping in/out of GUI (system-config-lvm) to add the following lines into
lvm configuration file is awkward.
# Type of locking to use. Defaults to file-based locking (1).
# Turn locking off by setting to 0 (dangerous: risks metadata corruption
# if LVM2 commands get run concurrently).
locking_type = "2"
locking_library = "/usr/lib/liblvm2clusterlock.so"
It would be nice to include the above into system-config-lvm tool (consider
this as a feature request). On the other hand, make really sure this is
documented in SysAdmin guide (if we have one).
The plan is to handle this by adding post/postun scripts to the clvm rpm to add
and remove, respectively, the locking type change required for clustered
operation to work with lvm2.
A modified version of the clvmd_fix_conf.sh script has been checked into
upstream cvs, called lvmconf, that handles adding and removing the clvm enabling
config file options. This script will be run by the lvm2-cluster %post
scriptlet to enable clvm, and the %preun scriptlet to remove it if the user is
uninstalling the package.
This fix is in lvm2-cluster-2.01.09-4.0.RHEL4 which should be in RHEL4-U2.