Description of problem: Change-logging is off by default, when enabled could crash at time. This is because of a bug an incomplete routine completion during init(). Version-Release number of selected component (if applicable): mainline
REVIEW: http://review.gluster.org/5380 (features/changelog: fixes when enabling changelog) posted (#1) for review on master by Venky Shankar (vshankar)
COMMIT: http://review.gluster.org/5380 committed in master by Vijay Bellur (vbellur) ------ commit 131d78dd36bac795d50fee3b04969b5ea9cb613c Author: Venky Shankar <vshankar> Date: Wed Jul 24 00:01:19 2013 +0530 features/changelog: fixes when enabling changelog Other enhancements being: * ignore fops made by rebalance * ignore internally triggered fops BUG: 987734 Change-Id: I7dd164ae3c209fdb8ec43a27e67b8846f937c93b Signed-off-by: Venky Shankar <vshankar> Reviewed-on: http://review.gluster.org/5380 Reviewed-by: Amar Tumballi <amarts> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/5921 (features/changelog: fixes when enabling changelog) posted (#1) for review on release-3.4 by Avra Sengupta (asengupt)
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user