Bug 492989 - executing group_tool dump gfs causes gfs_controld to spin on CPU
Summary: executing group_tool dump gfs causes gfs_controld to spin on CPU
Keywords:
Status: CLOSED DUPLICATE of bug 444529
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman
Version: 5.2
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-31 03:34 UTC by Dale Mosby
Modified: 2009-04-16 22:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-01 16:26:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.