Description of problem: I've two tests - smoke and centos regression [1][2]- that were aborted due to deadlock in Glusterfs processes. However, output from console doesn't give either backtrace or core of the process aborted. It would be helpful if we can get cores. [1] https://build.gluster.org/job/centos6-regression/6332/console [2] https://build.gluster.org/job/smoke/37110/ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I'm guessing this means it wasn't a crash. The best way to do this would be to attach gdb to the process to generate the core, yes?
(In reply to Nigel Babu from comment #1) > I'm guessing this means it wasn't a crash. The best way to do this would be > to attach gdb to the process to generate the core, yes? That, or run 'gcore $PID' and 'gstack $PID' to make it a little easier.
Is there a preferred command to get the right PID?
(In reply to Nigel Babu from comment #3) > Is there a preferred command to get the right PID? I don't think so, that would require guessing what process hangs. You probably need to capture the stack+core from all gluster processes.
We will no longer have hangs because of the per patch timeout. Closing this bug.