[Gluster-users] Replacing a failed brick

[David Gibbons]

Joe,

Now I understand what is going on here. Makes a lot more sense that it's a
bug in the sanity checking code. Thanks so much!

Dave


On Fri, Aug 16, 2013 at 11:19 AM, Joe Julian <joe at julianfamily.org> wrote:

> This tells you that this brick isn't running. That's probably because it
> was formatted and lost it's volume-id extended attribute. See
> http://www.joejulian.name/**blog/replacing-a-brick-on-**glusterfs-340/<http://www.joejulian.name/blog/replacing-a-brick-on-glusterfs-340/>
>
> Once that's fixed, on 10.250.4.65:
>
>
>   gluster volume start test-a force
>
>
> On 08/16/2013 08:03 AM, David Gibbons wrote:
>
>> Brick 10.250.4.65:/localmnt/g2lv5   N/A     N       N/A
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130818/1626d768/attachment.html>