Bug 231979

Summary: clvmd does not recover locks when restarting
Product: Red Hat Enterprise Linux 4 Reporter: Christine Caulfield <ccaulfie>
Component: lvm2Assignee: Milan Broz <mbroz>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: agk, ccaulfie, dwysocha, jbrassow, mbroz, prockai, pvrabec, rkenna
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0287 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-08 00:16:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christine Caulfield 2007-03-13 13:24:08 UTC 
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

How reproducible:
every time

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

Actual results:
step #6 shows no locks

Expected results:
The same locks as shown in step #3

Additional info:

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.
Comment 1 Jonathan Earl Brassow 2007-03-13 14:54:21 UTC 
*** Bug 231995 has been marked as a duplicate of this bug. ***
Comment 2 Christine Caulfield 2007-03-13 15:38:36 UTC 
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
done
Comment 11 Red Hat Bugzilla 2007-05-08 00:16:41 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2007-0287.html