Re: Dead directory after other node is rebooted

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

 




On 09/10/2014 08:32 AM, French Teddy wrote:
I have a very simple two nodes setup.

After I rebooted one the nodes, a directory deep inside the hierarchy on
the other node has become dead. By dead I mean any process trying to
access its content becomes stuck.

Absolutly nothing appears on the logs.

How can I fix that very very quickly?
Does the stuck process come out eventually? Or is it stuck forever?
How many files are under this directory? Could you please provide the output of
'getfattr -d -m. -e hex <dir/path/on/bricks>'

Pranith

TIA

greg

gluster 3.3.2 on debian 7.5
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.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