Bug 762645 (GLUSTER-913) - NFS-specific log analyzer tool
Summary: NFS-specific log analyzer tool
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-913
Product: GlusterFS
Classification: Community
Component: scripts
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-10 04:38 UTC by Shehjar Tikoo
Modified: 2015-12-01 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shehjar Tikoo 2010-05-10 04:38:10 UTC 
Most of the time, a NFS request and the reply are separated by hundreds
of lines of other debugging output most of which is not always relevant
for NFS debugging. This script synthesizes the full glusterfs log into
the parts relevant for NFS while bringing together the NFS requests with
there replies on one line.

Min log-level required for this script to be useful is DEBUG. Only
works for NFS translator.
Comment 1 Anand Avati 2010-05-10 06:18:11 UTC 
PATCH: http://patches.gluster.com/patch/3246 in master (extras: Add NFS-specific log analyzer tool)
Comment 2 Anand Avati 2010-06-01 04:24:04 UTC 
PATCH: http://patches.gluster.com/patch/3359 in master (extras/gnfs-lognalyzer: Delete class instance to release mem early)
Comment 3 Anand Avati 2011-05-11 23:18:15 UTC 
PATCH: http://patches.gluster.com/patch/6934 in master (gnfs-loganalyse: Track fh & entry operations given filename)
Comment 4 Anand Avati 2011-06-01 02:52:23 UTC 
PATCH: http://patches.gluster.com/patch/6935 in release-3.1 (gnfs-loganalyse: Track fh & entry operations given filename)
Note You need to log in before you can comment on or make changes to this bug.