Description of problem: With a 2-brick distributed volume, performing a remove-brick start successfully transfers files, but remove-brick status shows 0 rebalanced-files. Version-Release number of selected component (if applicable): CentOS 6 and FreeBSD 10 3.7.13 How reproducible: easily Steps to Reproduce: [root@colossus bricks]# gluster volume create removebricktest 192.168.110.1:/tank/bricks/rbt 192.168.110.2:/ftp/bricks/rbt volume create: removebricktest: success: please start the volume to access data [root@colossus bricks]# gluster volume start removebricktest volume start: removebricktest: success [root@colossus bricks]# mount -t glusterfs 192.168.110.2:/removebricktest /mnt/test [root@colossus bricks]# cd /mnt/test [root@colossus test]# ls [root@colossus test]# touch file{1..100} [root@colossus test]# ls file*| wc -l 100 [root@colossus test]# ls /ftp/bricks/rbt/file*| wc -l 28 [root@colossus2 ~]# ls /tank/bricks/rbt/file*| wc -l 72 [root@colossus test]# gluster volume remove-brick removebricktest 192.168.110.2:/ftp/bricks/rbt start volume remove-brick start: success ID: c88553ba-7372-4706-bafb-b1b0e4aea9ba [root@colossus test]# ls /ftp/bricks/rbt/file*| wc -l 28 [root@colossus2 ~]# ls /tank/bricks/rbt/file*| wc -l 100 [root@colossus test]# gluster volume remove-brick removebricktest 192.168.110.2:/ftp/bricks/rbt status Node Rebalanced-files size scanned failures skipped status run time in h:m:s --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 0 0Bytes 28 0 0 completed 0:0:0 Actual results: 0 rebalanced-files Expected results: 28 rebalanced-files Additional info:
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.