I'm using 3.7.11, this command works with me,
!remove-brick
[root@node2 ~]# gluster volume remove-brick v1 replica 2 192.168.3.73:/gfs/b1/v1 force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success
[root@node2 ~]# gluster volume remove-brick v1 replica 2 192.168.3.73:/gfs/b1/v1 force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success
Don't know about the commit thingy...
On Thursday, July 28, 2016 3:47 PM, Richard Klein (RSI) <rklein@xxxxxxxxxx> wrote:
We are using Gluster 3.7.6 in a replica 2 distributed-replicate configuration. I am wondering when we do a remove-brick with just one brick pair will the data be moved off the bricks once the status show complete and then you do the commit? Also, if you start a remove-brick process can you stop it? Is there an abort or stop command or do you just don’t do the commit?
Any help would be appreciated.
Richard Klein
RSI
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
