<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 22, 2016 at 12:38 PM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@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=""><br>
<br>
On 03/22/2016 12:23 PM, ABHISHEK PALIWAL wrote:<br>
><br>
> On Tue, Mar 22, 2016 at 12:14 PM, Gaurav Garg <<a href="mailto:ggarg@redhat.com">ggarg@redhat.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:ggarg@redhat.com">ggarg@redhat.com</a>>> wrote:<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>
> remove-brick without force option will perform task based on your<br>
> option,<br>
> for eg. remove-brick start option will start migration of file from<br>
> given<br>
> remove-brick to other available bricks in the cluster. you can check<br>
> 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<br>
> from the cluster.<br>
> It will result in data loss in case of distributed volume, because<br>
> it will not migrate file<br>
> from given remove-brick to other available bricks in the cluster. In<br>
> case of replicate volume<br>
> you might not have problem by doing remove-brick force because later<br>
> on after adding brick you<br>
> can issue heal command and migrate file from first replica set to<br>
> this newly added brick.\<br>
><br>
><br>
> so when you are saying the forcefully remove the brick means it will<br>
> remove the brick even when<br>
> that brick is not available or available but have the different uuid of<br>
> peers, without generating any error?<br>
</div></div>As I mentioned earlier it doesn't make sense to differentiate between<br>
these two behaviors until the UUID mismatch issue is resolved.<br></blockquote><div><br></div><div>Yes, I agree. but how we can resolve that uuid mismatch issue is there any way for the same in running system? <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="">><br>
><br>
> Thanks,<br>
><br>
> ~Gaurav<br>
><br>
> ----- Original Message -----<br>
> From: "ABHISHEK PALIWAL" <<a href="mailto:abhishpaliwal@gmail.com">abhishpaliwal@gmail.com</a><br>
</span><span class="">> <mailto:<a href="mailto:abhishpaliwal@gmail.com">abhishpaliwal@gmail.com</a>>><br>
> To: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a> <mailto:<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>>,<br>
> <a href="mailto:gluster-devel@gluster.org">gluster-devel@gluster.org</a> <mailto:<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<br>
> 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<br>
> the 'force' option it means it should remove the brick in any<br>
> 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>
> _______________________________________________<br>
> Gluster-users mailing list<br>
</span>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>><br>
<div class="HOEnZb"><div class="h5">> <a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
><br>
><br>
><br>
><br>
> --<br>
><br>
><br>
><br>
><br>
> Regards<br>
> Abhishek Paliwal<br>
><br>
><br>
> _______________________________________________<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>
><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>