Red Hat Bugzilla – Bug 844644
Replace brick doesn't work when the volume is stopped
Last modified: 2015-11-03 18:04:37 EST
Description of problem:
Currently replace brick only works when the volume is Started. I think it should still alow the replace brick when the volume is stopped. In a general case if I wish there are no writes when I start the replace brick, I would stop the volume and will do a replace brick which is currently not supported.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Stop the volume
2.Try to replace brick with the cli "volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> start"
[root@unused ~]# gluster
gluster> volume replace-brick vol0 10.70.1.115:/root/bricks/b1 10.70.1.115:/root/bricks/b4 start
volume: vol0 is not started
this fails because replace-brick tries to do the data-migration... try replace 'commit force' for the expected behavior of yours...