[Gluster-users] Replace replicate in single brick

[Andrus, Brian Contractor]

Gandalf,

From what I see, it doesn’t:
reset-brick <volname> <hostname:brick-path>

He showed the syntax for ‘replace-brick’ not ‘reset-brick’, which, since I am on 3.8.5, hopefully works when a source-brick is missing….
Anyone know if that would be true? Or do I have to upgrade to 3.9 to be able to replace a completely unavailable, missing brick replica?

I guess I will find out, since I could put the old disk back in with the errors if it must exist.

Brian

From: Gandalf Corvotempesta [mailto:gandalf.corvotempesta at gmail.com]
Sent: Tuesday, January 10, 2017 12:31 AM
To: Ravishankar N <ravishankar at redhat.com>
Cc: gluster-users at gluster.org; Andrus, Brian Contractor <bdandrus at nps.edu>
Subject: Re: [Gluster-users] Replace replicate in single brick

Il 10 gen 2017 05:59, "Ravishankar N" <ravishankar at redhat.com<mailto:ravishankar at redhat.com>> ha scritto:
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.
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.
-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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20170110/118fd272/attachment.html>