Description of problem: ======================= When one of brick is down due to underlying filesystem (here xfs) crash, volume stop is failing with error message "volume stop: Dis: failed: brick operations failed" Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.7.9-1 How reproducible: ================= Always Steps to Reproduce: =================== 1. Have one node cluster 2. Create 1*2 volume and start it. 3. crash underlying filesystem for one of the volume brick using "godown tool" 4. Check brick is down using "volume status" 5. Try to stop the volume // it will fail. Actual results: =============== Volume stop is failing with error message "volume stop: Dis: failed: brick operations failed" Expected results: ================= Volume stop should work properly. Additional info: ================
Providing devel_ack+ since BZ has been categorized as Regression.
I've the RCA now and the commit message of http://review.gluster.org/#/c/13965 explains it. Since the upstream patch is posted for review moving the status to Post.
3.7 patch : http://review.gluster.org/#/c/13973 posted for review.
Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/71623/
(In reply to Atin Mukherjee from comment #6) > Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/71623/ This is a wrong link, ignore. Correct link is https://code.engineering.redhat.com/gerrit/#/c/72433/
Downstream patch is merged now.
Verified this bug using the build "glusterfs-3.7.9-2.el7rhgs". Repeated the steps specified in description section. 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