Hide Forgot
Need to integrate the kbase article "How can I gather GFS2 lockdump information from RHEL 5 to send to Red Hat Support?" into official product docs. Link to kbase article: https://access.redhat.com/kb/docs/DOC-34401
Is this not a dup of bug #712392?
No, this is the GFS2 kbase article. Bug #712392 is the GFS kbase article. Since there are two separate articles that need to be incorporated, there are two separate bugs. :-) Thanks, -Allison
Updating the title, so its more obvious that the difference is GFS/GFS2 rather than can/do.
Re-assigning to me, since this is a GFS2 manual issue, but this is the first I've seen of this bug and it's past the 5.8 development phase so I'm moving this to 5.9.
Adding Shane Bradley and Adam Drew to the CC list for this BZ, which is a parallel BZ to BZ#712392 but for GFS2.
I'd suggest using the procedure in this kbase: "What data do I gather if processes accessing GFS2 are hung?" https://access.redhat.com/kb/docs/DOC-42333 As apposed to DOC-34401. In fact I'd thought I'd "unpublished" DOC-34401 from public view. While DOC-34401 captures good data it is a difficult multi-step procedure and is tough for a customer to reasonably accommodate during a production outage. The process in DOC-42333 is a single script that the customer can run that gathers all required data. The process is simpler for the customer and the data is delivered to us in an easier to use and easier to understand format. DOC-42333 is the only procedure I provide customers and the experience with it has been roundly positive. Another thing to consider (and Steve is the ultimate arbiter on this question) is that we may just want to package that script into gfs2-utils so that the customer has the data gathering script on their system by default. The procedure then would be as simple as sosreport - run the command, send us the tarballs. Note: I wrote a GFS2 sosreport plugin that gathers a subset of this data but the data gathering script in DOC-42333 is far more robust and wouldn't fit as a sosreport plugin.
Adam: Thanks for the updated link. For the GFS procedure, going to the old link automatically brought me to the updated document (which is why I noticed that the information had been changed), but that wasn't so for this GFS2 procedure. Whatever I write up here will be for both RHEL 5 and RHEL 6, but maybe I should wait until Steve Whitehouse weighs in on packaging the script before doing much work here on adding this to the GFS2 document.
Engineering and GSS discussed this and we're going to create a new bug to track the process of possibly including the gfs2 data gathering script I wrote into gfs2-utils. Will make this bug depend on that bug as the documentation will need to reflect the new tool if and when it becomes available.
Ok, then for now I won't try to write up the current kBase procedure for the gfs2 document (rhel 5 or rhel 6).
I refined the script and got it committed to gfs2-utils upstream. I'm going to be back-porting it to RHEL. The RHEL 6 BZ for that is here: https://bugzilla.redhat.com/show_bug.cgi?id=782801 The RHEL 5 BZ is here: https://bugzilla.redhat.com/show_bug.cgi?id=782804 We'll want to wait on the documentation until those are resolved. The tool may not make it into RHEL 5 due to how late in the lifecycle it is, but I'd like it if it did...
Changing the component to Documentation-cluster.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.