Red Hat Bugzilla – Bug 149080
clvmd-gulm locking is broken
Last modified: 2010-01-11 23:03:13 EST
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
Version-Release number of selected component (if applicable):
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
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
*** This bug has been marked as a duplicate of 146056 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.