Description of problem: ======================= Restarting glusterd after rebalance is completed, and on checking rebalance status , it shows that rebalance is in progress even though there are no files which are rebalanced Version-Release number of selected component (if applicable): ============================================================ glusterfs 3.4.0.44.1u2rhs How reproducible: ================= always Steps to Reproduce: =================== 1.Create a distribute volume with 3 bricks and start it 2.Fuse mount the volume and create files 3.Add bricks and start rebalance 4.After rebalance is completed , stop and start glusterd [root@boost d3]# gluster v rebalance vol3 status Node Rebalanced-files size scanned failures skipped status run time in secs --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 0 0Bytes 100 0 0 completed 0.00 10.70.34.88 0 0Bytes 100 0 0 completed 0.00 10.70.34.86 0 0Bytes 100 0 0 completed 0.00 volume rebalance: vol3: success: [root@boost d3]# service glusterd stop Stopping glusterd: [ OK ] [root@boost d3]# service glusterd start Starting glusterd: [ OK ] 5. Check rebalance status immediately . Status shows rebalance is 'in progress'. [ Rebalance was NOT STARTED after restarting glusterd and there are no files being rebalanced ] gluster v rebalance vol3 status Node Rebalanced-files size scanned failures skipped status run time in secs --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 0 0Bytes 0 0 0 in progress 0.00 10.70.34.88 0 0Bytes 0 0 0 in progress 0.00 10.70.34.86 0 0Bytes 100 0 0 completed 0.00 volume rebalance: vol3: success: Actual results: =============== Rebalance status shows it is in progress after restarting glusterd (no files being rebalanced and no rebalance start command executed) Expected results: ================= After restarting glusterd , rebalance status should show the previous rebalance operation completed unless a new add brick or rebalance start is executed . Additional info:
sosreports : http://rhsqe-repo.lab.eng.blr.redhat.com/bugs_necessary_info/1040345/
Cloning this to 3.1. to be fixed in future release.