<div dir="auto"><div class="gmail_extra" dir="auto"><div class="gmail_quote">Il 10 gen 2017 05:59, "Ravishankar N" <<a href="mailto:ravishankar@redhat.com">ravishankar@redhat.com</a>> ha scritto:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="quoted-text">
<div class="m_3837751820612318307moz-cite-prefix">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 <a class="m_3837751820612318307moz-txt-link-freetext" href="http://review.gluster.org/#/c/12250/" target="_blank">http://review.gluster.org/#/c/<wbr>12250/</a> gives you
some information on the steps to run.<br></div></div>
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.<br>
-Ravi<br></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">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? </div><div dir="auto">It would always be the same, if different, replace-brick command should be used.</div><div class="gmail_extra" dir="auto"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"></div></blockquote></div></div></div>