Red Hat Bugzilla – Bug 231979
clvmd does not recover locks when restarting
Last modified: 2013-02-28 23:05:44 EST
Description of problem:
When the daemon restarts, clvmd is supposed to re-acquire locks related to LVs
that are active on that node. This is no longer happening as the 'lvs' command
sematics changed some time ago.
Version-Release number of selected component (if applicable):
All current versions of LVM
Steps to Reproduce (on RHEL4):
1. activate some cluster LVs
2. # echo "clvmd" >/proc/cluster/dlm_locks
3. # cat /proc/cluster/dlm_locks
4. # killall clvmd
5. # clvmd
6. # cat /proc/cluster/dlm_locks
step #6 shows no locks
The same locks as shown in step #3
This is down to the way that the 'lvs' command has changed.
When clvmd starts up it issues an command: lvs --nolocking to get a list of
logical volumes. Only this command now does not show clustered LVs - merely an
error stating that it won't!
We need either --nolocking to show all LVs, or some other switch that will
display clustered LVs without a locking attempt being made.
--ignorelockingfailure is not an option because it attempts to call into
clvmd...which is busy trying to start up.
*** Bug 231995 has been marked as a duplicate of this bug. ***
no_locking should be a clustered locking mode.
Checking in lib/locking/no_locking.c;
/cvs/lvm2/LVM2/lib/locking/no_locking.c,v <-- no_locking.c
new revision: 1.11; previous revision: 1.10
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.