<div dir="ltr"><div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 22, 2016 at 12:14 PM, Gaurav Garg <span dir="ltr"><<a href="mailto:ggarg@redhat.com" target="_blank">ggarg@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">>> I just want to know what is the difference in the following scenario:<br>
<br>
1. remove-brick without the force option<br>
2. remove-brick with the force option<br>
<br>
<br>
</span>remove-brick without force option will perform task based on your option,<br>
for eg. remove-brick start option will start migration of file from given<br>
remove-brick to other available bricks in the cluster. you can check status<br>
of this remove-brick task by issuing remove-brick status command.<br>
<br>
But remove-brick with force option will just forcefully remove brick from the cluster.<br>
It will result in data loss in case of distributed volume, because it will not migrate file<br>
from given remove-brick to other available bricks in the cluster. In case of replicate volume<br>
you might not have problem by doing remove-brick force because later on after adding brick you<br>
can issue heal command and migrate file from first replica set to this newly added brick.\<br></blockquote><div><br></div><div>so when you are saying the forcefully remove the brick means it will remove the brick even when<br></div><div>that brick is not available or available but have the different uuid of peers, without generating any error? <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<br>
~Gaurav<br>
<div class="HOEnZb"><div class="h5"><br>
----- Original Message -----<br>
From: "ABHISHEK PALIWAL" <<a href="mailto:abhishpaliwal@gmail.com">abhishpaliwal@gmail.com</a>><br>
To: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>, <a href="mailto:gluster-devel@gluster.org">gluster-devel@gluster.org</a><br>
Sent: Tuesday, March 22, 2016 11:35:52 AM<br>
Subject: [Gluster-users] Impact of force option in remove-brick<br>
<br>
Hi Team,<br>
<br>
I have the following scenario:<br>
<br>
1. I have one replica 2 volume in which two brick are available.<br>
2. in such permutation and combination I got the UUID of peers mismatch.<br>
3. Because of UUID mismatch when I tried to remove brick on the second board I am getting the Incorrect Brick failure.<br>
<br>
Now, I have the question if I am using the remove-brick command with the 'force' option it means it should remove the brick in any situation either the brick is available or its UUID is mismatch.<br>
<br>
I just want to know what is the difference in the following scenario:<br>
<br>
1. remove-brick without the force option<br>
2. remove-brick with the force option<br>
<br>
<br>
Regards<br>
Abhishek<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><br><br><br><br>Regards<br>
Abhishek Paliwal<br>
</div></div>
</div></div>