[Gluster-users] Replacing a failed brick

[Joe Julian]

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/

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