Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 237386

Summary: clvmd and quorum disk prevents lvextend/lvremove
Product: Red Hat Enterprise Linux 5 Reporter: Scott Bachmann <bachmann>
Component: lvm2-clusterAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: agk, alain.richard, ccaulfie, dwysocha, jbrassow, mbroz, prockai
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0518 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-07 19:10:15 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:
Attachments:
Description Flags
Proposed patch to fix none

Description Scott Bachmann 2007-04-21 18:05:39 UTC 
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 
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223519">#223519</a> 
and 
<a 
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234589">#235689</a>

Version-Release number of selected component (if applicable):
lvm2-cluster-2.02.16-3.el5 (RHEL5 Stock)

How reproducible:
Very

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"
  
Actual results:
Error locking on node /dev/dm-3: Command timed out
Failed to suspend lv-website

Expected results:
Logical volume lv-website successfully resized

Additional info:
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).
Comment 1 Christine Caulfield 2007-04-23 13:33:39 UTC 
Created attachment 153280 [details]
Proposed patch to fix
Comment 2 Scott Bachmann 2007-04-23 14:41:57 UTC 
Hi Patrick,

I applied the proposed patch to the lvm2-cluster-2.02.16-3.el5 source RPM, and 
it does indeed resolve the issues.

Thanks!
Scott
Comment 3 Christine Caulfield 2007-04-23 14:56:09 UTC 
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
done
Comment 4 Kiersten (Kerri) Anderson 2007-04-23 17:30:50 UTC 
Fixing Product Name.  Cluster Suite components were integrated into the
Enterprise Linux version 5.0.
Comment 6 RHEL Program Management 2007-05-01 17:30:34 UTC 
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
release.
Comment 8 Christine Caulfield 2007-09-25 07:06:01 UTC 
*** Bug 299871 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2007-11-07 19:10:15 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-0518.html