Bug 492989

Summary: executing group_tool dump gfs causes gfs_controld to spin on CPU
Product: Red Hat Enterprise Linux 5 Reporter: Dale Mosby <dmosby>
Component: cmanAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.2CC: cluster-maint, edamato, emcnabb, teigland
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-01 16:26:28 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:

Description Dale Mosby 2009-03-31 03:34:37 UTC
Description of problem:
We attempted to use "group_tool dump gfs" to gather
information in the investigation of a gfs problem.
We found that running this just once causes the
gfs_controld process to spin consuming a CPU resource.
The only fix was to reboot.

Version-Release number of selected component (if applicable):
cman-2.0.84-2.el5

How reproducible:
Happens every time.

Steps to Reproduce:
1. Execute command:   group_tool dump gfs

  
Actual results:
Output from group_tool is sent to stdout.
One CPU will now show gfs_controld consuming all CPU time.

Expected results:
The gfs_controld process should behave normally
and not consume all cpu time.

Additional info:

Comment 1 David Teigland 2009-04-01 16:26:28 UTC

*** This bug has been marked as a duplicate of bug 444529 ***