https://bugzilla.redhat.com/show_bug.cgi?id=1380247
Bug ID: 1380247
Summary: Get diagnostic information for aborted test runs
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Keywords: Triaged
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
> Dump from RaghavendraG's email
Do we collect any diagnostic information before aborting tests as in [1]? If
yes, where can I find them?
If no, I think following information would be useful
1. ps output of all relevant gluster processes and tests running on them (to
find status of processes like 'D' etc)
2. Statedump of client and brick processes (better to dump all information like
inodes, call-stack, etc)
3. coredump of client and brick processes
If you think any other information is helpful, please add to the list.
Some points to note are
* to enable dumping of all objects we need to do,
echo "all=yes" >> $statedumpdir/glusterdump.options
before we issue commands to collect statedumps.
* we need to do
# kill -SIGUSR1 <pid-of-mount-process>
to collect statedump of client process as there is no cli command to issue.
* for bricks,
[root@unused rhs-glusterfs]# gluster volume statedump
Usage: volume statedump <VOLNAME> [nfs|quotad]
[all|mem|iobuf|callpool|priv|fd|inode|history]
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=V1HeRo18GY&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-infra
