Il 10 gen 2017 05:59, "Ravishankar N" <ravishankar@xxxxxxxxxx> ha scritto:
If you are okay with using a different name for the brick, then there is `gluster volume replace-brick <volname> <hostname:old brick> <hostname:new brick> commit force`. I think this command works from glusterfs 3.7.10 onward.If you are using glusterfs 3.9 and want to give the replaced brick the same name as the old one, there is the reset-brick command. The commit message in http://review.gluster.org/#/c/12250/ gives you some information on the steps to run.
-Ravi
If reset-brick is used to replace a brick with another with the same name, why this command ask for both source and destination brick name?
It would always be the same, if different, replace-brick command should be used.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
