<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Jul 27, 2015 5:20 PM, "Vijay Bellur" <<a href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>> wrote:<br>
><br>
> On Monday 27 July 2015 04:53 PM, Atin Mukherjee wrote:<br>
>><br>
>><br>
>><br>
>> On 07/27/2015 03:38 PM, Iain Milne wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> Hopefully a fairly simple question:<br>
>>><br>
>>> If I have a 3.6 distributed replica-2 setup with four nodes of one brick<br>
>>> each (so A/B in replicate as are C/D) what is the process of commands I<br>
>>> need to run to replace B, with new brick E?<br>
>><br>
>> You can go for replace brick commit force option. Please note commit<br>
>> force can result into data loss. You would need to ensure that you copy<br>
>> the data from the failed brick to the new brick manually.<br>
>>><br>
>>><br>
><br>
> If you ensure that the brick being replaced is not the source for any pending self-heals, replace-brick commit force in a replicated volume is safe. self-healing would take care of re-populating data once a new brick is in place.<br>
Thanks Vijay for the correction. I missed out that its a replicated volume.<br>
><br>
> Regards,<br>
> Vijay<br>
><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">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</p>