Description of problem: glusterd is crashing when user enable bitrot on the volume. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. create a cluster of two node. 2. create plane distribute volume which is having brick only in first node. 3. start the volume form any node. 4. enable bitrot form second node which is not having any brick. glusterd will crash. Actual results: glusterd is crashing. Expected results: glusterd should not crash. Additional info:
REVIEW: http://review.gluster.org/10680 (bitrot: Volfile generation should not proceed if node don't have any brick.) posted (#1) for review on release-3.7 by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10664 (bitrot: Volfile generation should not proceed if node doesn't have any brick.) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10664 (bitrot: Volfile generation should not proceed if node doesn't have any brick.) posted (#3) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/10664 (bitrot: Volfile generation should not proceed if node doesn't have any brick.) posted (#4) for review on master by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/10664 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 3586581c6edf222daf836c99ce2a1a266dc741f8 Author: Gaurav Kumar Garg <ggarg> Date: Fri May 8 13:08:22 2015 +0530 bitrot: Volfile generation should not proceed if node doesn't have any brick. glusterd crashes when bitrot is enabled on a distributed volume from a node which doesn't host a brick. While generating volfile glusterd should check number of brick on that node. If node doesn't have any brick then graph generation for bitrot and scrubber should not proceed further. Change-Id: I2158113e20e93738cde2a22fd73f0ae6b22aae9e BUG: 1219784 Signed-off-by: Gaurav Kumar Garg <ggarg> Reviewed-on: http://review.gluster.org/10664 Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user