Red Hat Bugzilla – Bug 237386
clvmd and quorum disk prevents lvextend/lvremove
Last modified: 2010-01-11 23:08:55 EST
Description of problem:
When attempting to extend a logical volume (and other LV modifications), the
clvmd daemon attempts to contact all nodes in the cluster. If the cluster is
using a quorum disk, clvmd attempts to contact this "node" and times out.
This is the similar to bugs <a
Version-Release number of selected component (if applicable):
lvm2-cluster-2.02.16-3.el5 (RHEL5 Stock)
Steps to Reproduce:
1. Configure a cluster with a quorum disk
2. "service cman start" on both nodes
3. "service qdiskd start" on both nodes
4. "service clvmd start" on both nodes
5. "lvextend -L +4M /dev/vg-vms/lv-website"
Error locking on node /dev/dm-3: Command timed out
Failed to suspend lv-website
Logical volume lv-website successfully resized
These systems are running cman-2.0.60, with two additional patches from bugs
#223519 and #230972 for proper quorum disk functionality. The quorum disk is
not part of a LVM, and is /dev/dm-3 (as shown above).
Created attachment 153280 [details]
Proposed patch to fix
I applied the proposed patch to the lvm2-cluster-2.02.16-3.el5 source RPM, and
it does indeed resolve the issues.
Thanks for testing that,
Now checked in :
Checking in daemons/clvmd/clvmd-cman.c;
/cvs/lvm2/LVM2/daemons/clvmd/clvmd-cman.c,v <-- clvmd-cman.c
new revision: 1.17; previous revision: 1.16
Fixing Product Name. Cluster Suite components were integrated into the
Enterprise Linux version 5.0.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
*** Bug 299871 has been marked as a duplicate of this bug. ***
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.