[Gluster-devel] [Gluster-users] How do I replace a failed brick

Ravishankar N ravishankar at redhat.com
Fri Feb 27 02:01:45 UTC 2015


On 02/27/2015 07:10 AM, Cary Tsai wrote:
>
> Assume I have 4 bricks in a replica (count=2) volume:
>
> Volume Name: data-vol
>
> Number of Bricks: 2 x 2 = 4
>
> Brick1: 192.168.1.101/brick <http://192.168.1.101/brick>
>
> Brick2: 192.168.1.102/brick <http://192.168.1.102/brick>
>
> Brick3: 192.168.1.103/brick <http://192.168.1.103/brick>
>
> Brick4: 192.168.1.104/brick <http://192.168.1.104/brick>
>
> Something happens to Brick3 and I want to replace it by 
> 192.168.1.105/brick <http://192.168.1.105/brick>
>
> What command should I use to replace 192.168.1.103/brick 
> <http://192.168.1.103/brick> by 192.168.1.105/brick 
> <http://192.168.1.105/brick>?
>
> Can I use:
>
> gluster volume replace-brick data-vol 192.168.1.103/brick 
> <http://192.168.1.103/brick> 192.168.1.105/brick 
> <http://192.168.1.105/brick> commit force?
>

This is the correct choice. Since you have replaced a replica brick, you 
will have to follow up with 'gluster vol heal data-vol full` to restore 
data from 104/brick to 105/brick.

> Or I have to start _replace-brick_ first then commit it?
>
> Thanks,
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20150227/cf511788/attachment.html>


More information about the Gluster-devel mailing list