Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 250336 - RFE: add the ability to get a lockdump out of gfs through sysrq
RFE: add the ability to get a lockdump out of gfs through sysrq
Product: Red Hat Cluster Suite
Classification: Retired
Component: GFS-kernel (Show other bugs)
All Linux
high Severity low
: ---
: ---
Assigned To: Robert Peterson
Cluster QE
Depends On:
Blocks: 295531 295541
  Show dependency treegraph
Reported: 2007-07-31 17:27 EDT by Josef Bacik
Modified: 2010-01-11 22:18 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-25 13:38:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch that implements this functionality. (2.12 KB, patch)
2007-07-31 17:27 EDT, Josef Bacik
no flags Details | Diff

  None (edit)
Description Josef Bacik 2007-07-31 17:27:38 EDT
As more customers are starting to use GFS in a shared root environment its 
becoming more difficult to troubleshoot gfs hangs, as we cannot run gfs_tool 
lockdump because a GFS hang usually means the entire box is hung and the only 
way to get information is via sysrq.  This patch dumps glock information via 
sysrq.  I've tested this patch on my cluster and doesn't appear to blow 
anything up.
Comment 1 Josef Bacik 2007-07-31 17:27:38 EDT
Created attachment 160362 [details]
patch that implements this functionality.
Comment 3 Robert Peterson 2008-03-25 13:38:50 EDT
While I still feel this would be useful, it requires registering a new
sysrq sequence.  Since the sysrq sequences are designed and implemented
by the upstream community, and gfs1 is not upstream (nor will it ever be)
the decision was made to not implement this fix.  It would be too easy
for upstream to make changes that are not compatible with the fix.
So let's keep it a patch for now.

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