+++ This bug was initially created as a clone of Bug #843377 +++ Description of problem: When statedump of a volume is taken, io-threads translator specific information is not dumped in the statedump file of the brick processes. Version-Release number of selected component (if applicable): RHS 2.0 update 2 How reproducible: Steps to Reproduce: 1. get the statedump of the brick process ( kill -USR1 <brick-process-id>) 2. look for io-thread related info in the statedump (statedumps available in /tmp directory) Actual results: io-threads related information is missing Expected results: io-threads related information should be present in statedump Additional info: This bug is already rised over glusterfs 3.3.0 with Bug id - 843377
already fixed upstream, will be present in RHS-2.1. http://review.gluster.com/3736
statedump taken at server side (RHS side) has io-threads related information. (i.e) gluster volume statedump <vol-name> generates statedump file @ /var/run/gluster/<statedump-file>, and it contains io-threads related information. VERIFIED with glusterfs 3.4.0.12rhs.beta5-2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html