Bug 175033 - clustat reports Resource Group information unavailable after N gfs file systems are mounted
Summary: clustat reports Resource Group information unavailable after N gfs file syste...
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: magma-plugins   
(Show other bugs)
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
Depends On: 175372
TreeView+ depends on / blocked
Reported: 2005-12-05 21:00 UTC by Henry Harris
Modified: 2009-04-16 20:18 UTC (History)
1 user (show)

Fixed In Version: RHBA-2006-0172
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-06 20:30:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
magma-plugins was incorrectly reading /proc/cluster/services for sizes > 4096 (1.15 KB, patch)
2005-12-08 19:33 UTC, Lon Hohberger
no flags Details | Diff
Correct patch against 1.0.2/1.0.3 which reads in page sizes. (2.01 KB, patch)
2005-12-09 16:44 UTC, Lon Hohberger
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0172 normal SHIPPED_LIVE magma-plugins bug fix update 2006-01-06 05:00:00 UTC

Description Henry Harris 2005-12-05 21:00:35 UTC
Description of problem: After mounting somewhere between 15 and 23 GFS file 
systems, clustat reports Resource Group informatation unavailable

Version-Release number of selected component (if applicable):

How reproducible:
Every time when a certain number of GFS file systems are mounted.  On one 
cluster that number is 15.  On another cluster that number is 23.

Steps to Reproduce:
1. Run clustat and verify services are shown
2. Mount 23 GFS file systems
3. Run clustat and see "Reource Group information is unavailable"
Actual results:
Cluster services not shown

Expected results:
Cluster services shown

Additional info:

Comment 1 Lon Hohberger 2005-12-06 14:29:00 UTC
Was rgmanager still running, or did it crash?

Comment 2 Henry Harris 2005-12-06 15:56:53 UTC
It was still running.

Comment 3 Henry Harris 2005-12-06 21:13:22 UTC
Could this bug be related to bug #171153?  We have multiple applications that 
run on every node in the cluster that all run clustat at various times.  Can 
we get the fix you just referred to for bug #171153?

Comment 4 Lon Hohberger 2005-12-08 19:32:00 UTC
*** Bug 175099 has been marked as a duplicate of this bug. ***

Comment 5 Lon Hohberger 2005-12-08 19:33:55 UTC
Created attachment 122042 [details]
magma-plugins was incorrectly reading /proc/cluster/services for sizes > 4096

Comment 6 Lon Hohberger 2005-12-08 19:34:40 UTC
Setting component to magma-plugins

Comment 7 Lon Hohberger 2005-12-08 19:38:09 UTC
Patches in CVS, head, stable, rhel4 -- setting to modified.

Comment 9 Lon Hohberger 2005-12-09 16:30:34 UTC
The fix doesn't work; you can't read >1page from /proc at a time.

However, there's an issue with issuing multiple reads to /proc/cluster/services,
which I've set as a dependency to this bugzilla.  I can make the correct fix for
magma-plugins, but there's no guarantee it will work in all cases until #175372
is fixed.

Comment 10 Lon Hohberger 2005-12-09 16:44:24 UTC
Created attachment 122082 [details]
Correct patch against 1.0.2/1.0.3 which reads in page sizes.

Comment 11 Henry Harris 2005-12-10 00:52:08 UTC
This patch fixed the problem.  Thanks!

Comment 12 Henry Harris 2005-12-13 23:24:43 UTC
The rgmanager-1.9.43-0 and magma-plugins-1.0.3-0.3bz175033 seem to be causing 
other problems.  With a cluster configured for four nodes, if I bring up only 
three of the four nodes, the cluster does not get created even though there is 
quorum.  All three nodes start fenced but never return. 

Comment 13 Red Hat Bugzilla 2006-01-06 20:30:36 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.


Note You need to log in before you can comment on or make changes to this bug.