(Opening report to track this change properly for RHEL6 update, started originally in bug #1208523 and bug #1211507 comment #3)
lvmconf is just a helper script and new patches are adding new helper hooks to set HA LVM properly, not changing existing functionality - we may still squeeze this into 6.7 as users may benefit from easier configuration.
Just like we have lvmconf --enable-cluster which makes sure that locking_type=3 and use_lvmetad=0 is set in lvm.conf, add --enable-halvm to make sure that locking_type=1 and use_lvmetad=0 is set in lvm.conf.
Also, to remove burden from users, make it easier for them so they can also set proper state for services when switching to/from cluster/halvm.
The lvmconf script is now patched upstream and it provides these changes:
--> new "--enable-halvm" (sets locking_type=1 and use_lvmetad=0)
--> new "--disable-halvm" option (go backward - sets default locking type, which is locking_type=1 and default use_lvmetad which in case of RHEL6 is 0)
--> new "--services" option to handle Systemd/SysV services according to changes done in LVM configuration (in case of RHEL6, this encompasses lvm2-lvmetad, clvmd and cmirrord SysV services), this option causes the services to be enabled or disabled accordingly
--> new "--mirrorservice" option to handle cmirrord service in addition
--> new "--startstopservices" option to also start or stop services according to lvm.conf changes immediately
Marking this particular bug as VERIFIED with:
Additionally, a new bug has been opened (Bug 1213735) which deals with the more detailed command line options processing, and setting up of a locking_type properly in certain cases.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.