Bug 501987
| Summary: | RFE: Add event tracing to GFS2 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Steve Whitehouse <swhiteho> | |
| Component: | kernel | Assignee: | Steve Whitehouse <swhiteho> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Jenner <mjenner> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 6.0 | CC: | adas, bmarzins, rlerch, rpeterso, slevine | |
| Target Milestone: | rc | Keywords: | FutureFeature | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Event Tracing in GFS2
GFS2's event tracing is provided via the generic tracing infrastructure. The events are designed to be useful for debugging purposes. Note, however that it is not guaranteed that the GFS2 events will remain the same throughout the lifetime of Red Hat Enterprise Linux 6. Further details on GFS2's glocks and event tracing can be found in the following 2009 Linus Symposium paperhttp://kernel.org/doc/ols/2009/ols2009-pages-311-318.pdf
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 579598 (view as bug list) | Environment: | ||
| Last Closed: | 2009-12-15 10:30:12 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: | ||||
| Bug Depends On: | 489483, 501985 | |||
| Bug Blocks: | 519832, 579598 | |||
|
Description
Steve Whitehouse
2009-05-21 13:53:11 UTC
This is already in RHEL6. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: GFS2's event tracing is provided via the generic tracing infrastructure. The events are designed to be useful for debugging purposes. We do not guarantee that the GFS2 events will remain the same throughout the lifetime of RHEL6, however the structure of the events is such that they can be parsed in a generic manner, so this should not be a problem. Further details on GFS2's glocks and event tracing can be found in this 2009 Linus Symposium paper: http://kernel.org/doc/ols/2009/ols2009-pages-311-318.pdf BZ 579598 is a different bug --- the tracepoints info is not going into GFS2, but there was some other information that I found (about glocks) when I was reading Steve W's technical papers that I thought I could use to clarify some info he had given me earlier about glocks. It's a separate subject. It's just a matter of added a couple of tables, from his technical paper.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,3 +1,3 @@
-GFS2's event tracing is provided via the generic tracing infrastructure. The events are designed to be useful for debugging purposes. We do not guarantee that the GFS2 events will remain the same throughout the lifetime of RHEL6, however the structure of the events is such that they can be parsed in a generic manner, so this should not be a problem.
+Event Tracing in GFS2
-Further details on GFS2's glocks and event tracing can be found in this 2009 Linus Symposium paper: http://kernel.org/doc/ols/2009/ols2009-pages-311-318.pdf+GFS2's event tracing is provided via the generic tracing infrastructure. The events are designed to be useful for debugging purposes. Note, however that it is not guaranteed that the GFS2 events will remain the same throughout the lifetime of Red Hat Enterprise Linux 6. Further details on GFS2's glocks and event tracing can be found in the following 2009 Linus Symposium paperhttp://kernel.org/doc/ols/2009/ols2009-pages-311-318.pdf
|