Description of problem: Removing multiple bricks at the same time causes data loss Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create a distribute volume with 3 bricks 2. fill up with some data and count the number of files created 3. Now start remove-brick after the remove-brick completes commit the operation 4. check the number of files on the mount point Actual results: After Remove-brick commit causes data loss. Expected results: Additional info:
Remove multiple bricks at the same time, actually this scenario is causing data loss.
not able to reproducible even in Shylesh's setup (also in my setup). Asked him to run it multiple times, if not reproduced, we should take this out from beta blocker
sent a patch for fixing the issue of remove-brick (more than 2 bricks involving two different nodes) at http://review.gluster.com/3173. Need to test this before committing. Shylesh, please fetch the patch and run the tests, confirm the behavior.
CHANGE: http://review.gluster.com/3173 (glusterd (remove-brick): fix data-loss issue) merged in master by Vijay Bellur (vijay)
Works fine on 3.3.0qa36