[Gluster-users] Replication not working on server hang

Justice London jlondon at lawinfo.com
Fri Aug 28 16:36:28 UTC 2009

Just wanted to chime in that the EXACT same issue has occurred for me. I was
going to work through the support chain but given that others are seeing it
and hopefully have logs, perhaps I don't need to do so.

Basically, I hope it can be fixed!

Justice London
E-mail:  jlondon at lawinfo.com

-----Original Message-----
From: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] On Behalf Of Stephan von
Sent: Friday, August 28, 2009 4:33 AM
To: David Saez Padros
Cc: Anand Avati; gluster-users
Subject: Re: [Gluster-users] Replication not working on server hang

> [...]
> Glusterfs log only shows lines like this ones:
> [2009-08-28 09:19:28] E [client-protocol.c:292:call_bail] data2: bailing 
> out frame LOOKUP(32) frame sent = 2009-08-28 08:49:18. frame-timeout =
> [2009-08-28 09:23:38] E [client-protocol.c:292:call_bail] data2: bailing 
> out frame LOOKUP(32) frame sent = 2009-08-28 08:53:28. frame-timeout =
> Once server2 has been rebooted all gluster fs become available
> again on all clients and the hanged df and ls processes terminate,
> but difficult to understand why a replicated share that must survive
> to failure on one server does not.

You are suffering from the problem we talked about few days ago on the list.
If your local fs produces a deadlock somehow on one server glusterfs is
currently unable to cope with the situation and just _waits_ for things to
come. This deadlocks your clients, too, without any need.
Your experience backs my critics on the handling of these situations.

Gluster-users mailing list
Gluster-users at gluster.org

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.409 / Virus Database: 270.13.70/2329 - Release Date: 08/28/09

More information about the Gluster-users mailing list