Document URL: ============= DHT: Once remove brick start failed in between Remove brick commit should not be allowed Steps: ======== 1. Create a distributed volume with three bricks and mount it on client using FUSE 2. From the mount point create lots of directories and one direcotry with 30k files 3. Remove one of the brick form the volume and while re-blance is in progress delete all directories and files from the mount point and due to this remove-brick operation failed 4.Though remove-brick operation failed remove-commint job is getting succeeded, Expected Result: ================ Remove-brick commit should be allowed only when the remove-brick operation job is passed
*** Bug 1330484 has been marked as a duplicate of this bug. ***
Mainline upstream : http://review.gluster.org/#/c/12513/ release-3.7 : http://review.gluster.org/#/c/12513/ Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/73466/
Verified the bug in glusterfs-3.7.9-5 commit fails with an error message. [root@dhcp46-103 ~]# gluster v remove-brick supernova 10.70.47.128:/bricks/brick1/sn 10.70.47.171:/bricks/brick1/sn 10.70.47.187:/bricks/brick1/sn 10.70.46.103:/bricks/brick1/sn status Node Rebalanced-files size scanned failures skipped status run time in h:m:s --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 0 0Bytes 0 0 0 completed 0:27:19 10.70.47.187 0 0Bytes 0 0 0 completed 0:29:12 10.70.47.171 0 0Bytes 0 0 0 completed 0:29:8 10.70.47.128 0 0Bytes 0 3 0 failed 0:7:17 [root@dhcp46-103 ~]# [root@dhcp46-103 ~]# gluster v remove-brick supernova 10.70.47.128:/bricks/brick1/sn 10.70.47.171:/bricks/brick1/sn 10.70.47.187:/bricks/brick1/sn 10.70.46.103:/bricks/brick1/sn commit Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y volume remove-brick commit: failed: Staging failed on 10.70.47.128. Error: use 'force' option as migration has failed - using force option indeed allowed to remove the brick [root@dhcp46-103 ~]# gluster v remove-brick supernova 10.70.47.128:/bricks/brick1/sn 10.70.47.171:/bricks/brick1/sn 10.70.47.187:/bricks/brick1/sn 10.70.46.103:/bricks/brick1/sn force Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y volume remove-brick commit force: success Moving the bug to verified.
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
*** Bug 1288448 has been marked as a duplicate of this bug. ***