Bug 149080 - clvmd-gulm locking is broken
Summary: clvmd-gulm locking is broken
Keywords:
Status: CLOSED DUPLICATE of bug 146056
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: lvm2-cluster
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-18 15:37 UTC by Christine Caulfield
Modified: 2010-01-12 04:03 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:08:12 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.