Re: brick crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi Pierre,
        Could you send volume info output of the volume where you are trying to do this operation and also point out which brick is giving problem.

Pranith
On 01/28/2016 08:55 PM, Pierre Léonard wrote:
Hi all,

I have a strip 7 volume of 14 nodes. one of the brick crash and I replace the failed disk. Nox on that node the brick is entirely new.

then when I want to start the volume gluster answer :

[root@xstoocky01 brick2]# gluster volume start gvscratch
volume start: gvscratch: failed: Staging failed on xstoocky02. Error: Failed to get extended attribute trusted.glusterfs.volume-id for brick dir /mnt/gvscratch/brick2. Reason : No data available


Which seem to be relatively honest. I can't remove the brick :

 gluster volume remove-brick gvscratch xstoocky02:/mnt/gvscratch/brick2 start
volume remove-brick start: failed: Remove brick incorrect brick count of 1 for stripe 7




 So how can I re-introduce that brick in the volume ?


Many thank's

Pierre Léonard



_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux