Description of problem: I did replace-brick in a distribute volume and 'replace-brick status' showed 'Migration complete'. After commit, I lost all files. Version-Release number of selected component (if applicable): How reproducible: # gluster volume create test1 192.168.122.2:/tmp/test1-b1 # gluster volume start test1 # mount -t glusterfs 192.168.122.2:test1 /mnt # cp -avi /etc/* /mnt # umount /mnt # gluster volume replace-brick test1 192.168.122.2:/tmp/test1-b1 192.168.122.2:/tmp/test1-b2 start # gluster volume replace-brick test1 192.168.122.2:/tmp/test1-b1 192.168.122.2:/tmp/test1-b2 status volume replace-brick: success: Number of files migrated = 0 Migration complete # gluster volume replace-brick test1 192.168.122.2:/tmp/test1-b1 192.168.122.2:/tmp/test1-b2 commit # mount -t glusterfs 192.168.122.2:test1 /mnt # ls -la /mnt missing files Expected results: All files need to be in new brick and available on mounting Additional info: I see 'Number of files migrated = 0', this could be the reason for missing files
keeping replace-brick issues with KP. Btw, upstream replace-brick is in discussion for removal : http://www.gluster.org/pipermail/gluster-users/2012-October/034473.html (its not yet finalized), so upstream may not be a good place for testing of replace-brick yet.
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.