Bug 567317

Summary: groupd dlm:clvmd stuck in LEAVE_STOP_WAIT
Product: Red Hat Enterprise Linux 5 Reporter: Benjamin Kahn <bkahn>
Component: cmanAssignee: David Teigland <teigland>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.3CC: burghardt, casmith, ccaulfie, cluster-maint, cward, edamato, fnadge, jwest, pm-eus, rom, schlegel, tao, tdunnon, teigland
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: cman-2.0.115-1.el5_4.12 Doc Type: Bug Fix
Doc Text:
When the clvmd lockspace got assigned the groupd id ZERO, dlm_controld rejected it.This caused the groupd to be blocked on systems with large amounts of scsi devices. With this update, id ZERO is not anymore assigned to clvmd. clvmd can now join the domain with a valid id and correctly interact with dlm_controld.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-04 15:06:57 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:
Bug Depends On: 521817    
Bug Blocks:    

Description Benjamin Kahn 2010-02-22 16:08:16 UTC
This bug has been copied from bug #521817 and has been proposed
to be backported to 5.4 z-stream (EUS).

Comment 6 Florian Nadge 2010-08-04 12:52:27 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
When the clvmd lockspace got assigned the groupd id ZERO, dlm_controld rejected it.This caused the groupd to be blocked on systems with large amounts of scsi devices. With this update, id ZERO is not anymore assigned to clvmd. clvmd can now join the domain with a valid id and correctly interact with dlm_controld.

Comment 7 errata-xmlrpc 2010-08-04 15:06:57 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 therefore 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-2010-0596.html