Description of problem: ======================= glusterd restart is failing if volume brick is down due to underlying filsystem crash (XFS) Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.7.9-2. How reproducible: ================= Always Steps to Reproduce: =================== 1. Have one/two node cluster 2. Create 1*2 volume and start it. 3. crash underlying filesystem for one of the volume brick using "godown tool" OR any other way. 4. Check brick is down using "volume status" 5. Try glusterd restart //restart will fail. Actual results: =============== glusterd restart is failing if volume brick is down due to FS crash. Expected results: ================= glusterd restart should work. Additional info:
http://review.gluster.org/#/c/14075 is posted for review in upstream
Rahul/Alok, Please provide qe/pm_acks. ~Atin
Hi Alok, Could you provide the pm_ack on this bz? ~Atin
Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/73410/ Upstream mainline patch : http://review.gluster.org/14075 Upstream 3.7 patch : http://review.gluster.org/14124
verified this bug using the build "glusterfs-3.7.9-4". Repeated the reproducing steps mentioned, Fix is working good. Moving 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. https://access.redhat.com/errata/RHBA-2016:1240