Bug 149080

Summary: clvmd-gulm locking is broken
Product: [Retired] Red Hat Cluster Suite Reporter: Christine Caulfield <ccaulfie>
Component: lvm2-clusterAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: agk
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:08:12 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 2005-02-18 15:37:04 UTC
Description of problem:
The gulm module of clvm locking cannot cope with conversions - it
assumes all locks are new ones and so locks can get left around
because of the horrible hack it uses for mapping DLM lock modes onto
gulm ones.

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:
1. vgchange -an; vgchange -ay one one node
2. lvextend on that node
3. lvreduce on that node
    

Actual Results:  lvreduce hangs 

Expected Results:  non-hanging

Additional info:

Comment 1 Christine Caulfield 2005-02-21 14:37:59 UTC
Need to maniplate both locks when changing modes.

There's still something up with clvmd via gulm - I need Mike's help.

Checking in daemons/clvmd/clvmd-gulm.c;
/cvs/lvm2/LVM2/daemons/clvmd/clvmd-gulm.c,v  <--  clvmd-gulm.c
new revision: 1.10; previous revision: 1.9
done


Comment 2 Christine Caulfield 2005-02-28 15:48:38 UTC

*** This bug has been marked as a duplicate of 146056 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:08:12 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.