Gluster users - Sep 2014 - Dead directory after other node is rebooted

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?

TIA

greg

gluster 3.3.2 on debian 7.5

On 10/09/2014, at 4:02 AM, French Teddy wrote:
<snip>
> gluster 3.3.2 on debian 7.5

As a thought, this is a very old version of GlusterFS.  The oldest
series we generally "support" is the 3.4.x series at the moment.

That being said, someone might have ideas how to help.  I'm just
not technical enough to be one of them. ;)

Once you have it fixed though, it'd be a good idea to upgrade. :)

Regards and best wishes,

Justin Clift

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

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 at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users