[Gluster-users] Strange server locks isuess with 2.0.7 - updating

Raghavendra G raghavendra at gluster.com
Thu Nov 19 17:09:04 UTC 2009

Hi Marek,

Is it possible for you to provide a backtrace of the crash? And can you file a bug report at bugs.gluster.com? Also if possible can you upgrade to 2.8 release and confirm whether you face the same problem?

----- Original Message -----
From: "Marek" <mb at kis.p.lodz.pl>
To: gluster-users at gluster.org
Sent: Thursday, November 19, 2009 7:20:44 PM GMT +04:00 Abu Dhabi / Muscat
Subject: Re: [Gluster-users] Strange server locks isuess with 2.0.7 - updating

Andre Felipe Machado wrote:
> Hello,
> Try to disable flush behind option.
> It behaves *badly* with slow speed net, drives and machines...
> It can cause the cited lock up behaviour.
> Your server got caught in I/O dead lock.
> Regards.
> Andre Felipe Machado
> http://www.techforce.com.br

Thanks, we tried disable flush behind option (we switch to a default writebehind options) but after
a couple of hours glusterfs (on client) died with signall 11:

pending frames:
frame : type(1) op(LOOKUP)

patchset: v2.0.7
signal received: 11
time of crash: 2009-11-14 03:37:28
configuration details:
argp 1
backtrace 1
dlfcn 1
fdatasync 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 2.0.7
Version      : glusterfs 2.0.7 built on Nov  5 2009 12:49:05
git: v2.0.7
Starting Time: 2009-11-16 12:41:08
Command line : glusterfs --log-file=/var/log/gluster-client -f /usr/local/etc/glusterfs/glusterfs-client.vol /var/glustertest/
PID          : 28270
System name  : Linux
Nodename     : mb
Kernel Release :
Hardware Identifier: i686

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

More information about the Gluster-users mailing list