Red Hat Bugzilla – Bug 770346
Remove-brick commit operation causing data loss
Last modified: 2015-12-01 11:45:32 EST
Description of problem:
removing a brick looses all data from that brick
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create a distribute volume with 2 bricks
2.create some files and directories on the mount point
3.gluster volume remove-brick $vol $brick2 start
4. Once the status shows completed execute "gluster volume remove-brick $vol $brick2 commit"
Number of files decreased on the mount point after the operation
This feature should migrate the files to the remaining bricks and there should be no data loss
please update these bugs w.r.to 3.3.0qa27, need to work on it as per target milestone set.
This bug is still reproducible on 3.3.0qa27
(In reply to comment #1)
> please update these bugs w.r.to 3.3.0qa27, need to work on it as per target
> milestone set.
patch sent : http://review.gluster.com/2933
CHANGE: http://review.gluster.com/2933 (distribute-rebalance: fix the logic of ENOENT handling) merged in master by Vijay Bellur (firstname.lastname@example.org)
Data loss upon single brick removal is fixed, however removing multiple bricks at the same time has issues will log a new bug.