+++ This bug was initially created as a clone of Bug #846192 +++ Command line option is required to dump the event history.
gluster volume statedump <volname> history will dump the event history to the statedump file. As of now patches have been submitted to integrate event-history with fuse and trace xlators.
Bug verification blocked by 888238. so glusterd fails, when trying to issue the command - " gluster volume statedump <vol-name>". Unable to check the working of command - "gluster volume statedump <vol-name> history. Also fixed in version should be - glusterfs 3.4.0-qa6 and not glusterfs 3.4.0-qa5 Under all this conditions moving this bug to ASSIGNED state
(In reply to comment #3) > Bug verification blocked by 888238. > so glusterd fails, when trying to issue the command - " gluster volume > statedump <vol-name>". > Glusterd fails means is it crashing or the cli command failing? In either case can you attach the logs? > Unable to check the working of command - "gluster volume statedump > <vol-name> history. > > Also fixed in version should be - glusterfs 3.4.0-qa6 and not glusterfs > 3.4.0-qa5 > > Under all this conditions moving this bug to ASSIGNED state
bug 888238 is fixed in qa6 (and now the build is available) so moving the bug again to ON_QA state
Tested with glusterfs-3.4.0.11rhs-1 and it works well. Moving it to VERIFIED state
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