Red Hat Bugzilla – Bug 966847
glusterfs crashed while collecting the sosreport
Last modified: 2016-02-17 19:19:56 EST
REVIEW: http://review.gluster.org/4968 (statedump: Print entries in cb buffer in FIFO order) posted (#3) for review on master by Shishir Gowda (email@example.com)
REVIEW: http://review.gluster.org/4968 (statedump: Print entries in cb buffer in FIFO order) posted (#4) for review on master by Shishir Gowda (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/4968 committed in master by Vijay Bellur (email@example.com)
Author: shishir gowda <firstname.lastname@example.org>
Date: Wed May 8 17:37:00 2013 +0530
statedump: Print entries in cb buffer in FIFO order
Currently cb buffer was being printed in LIFO order, which
is was against the percieved notion of logs having older
entries printed before newer entries in the state dumps.
Re-did the loop to prevent crash as when w_index == 0, we
would access cb[w_index - 1].
Signed-off-by: shishir gowda <email@example.com>
Reviewed-by: Santosh Pradhan <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Vijay Bellur <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.