[Gluster-users] A glusterfsd process crashed(?)

Isamu SUZUKI cham.glusterfs at yottac.com
Thu Jul 31 08:50:34 UTC 2014


Hello guys,

I'm an administrator of our GlusterFS replicated storage on AWS.
The version of GlusterFS is 3.4.1 ( all gluster servers and all clients )

A process of glusterfsd crashed.
And the same process crashed too  after 1 month of the former crashed.

I've checked /var/log/glusterfs/bricks/our-context.log.

--------------
pending frames:
frame : type(0) op(28)

patchset: git://git.gluster.com/glusterfs.git
signal received: 11
time of crash: 2014-07-29 02:26:23configuration 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 3.4.1
/lib64/libc.so.6(+0x349c0)[0x7f47d92fb9c0]
/usr/lib64/libglusterfs.so.0(+0x2be0c)[0x7f47da089e0c]
/usr/lib64/libglusterfs.so.0(+0x2bf4c)[0x7f47da089f4c]
/usr/lib64/libglusterfs.so.0(inode_unref+0x3c)[0x7f47da08a32c]
/usr/lib64/libglusterfs.so.0(gf_dirent_free+0x48)[0x7f47da099508]
/usr/lib64/glusterfs/3.4.1/xlator/storage/posix.so(posix_do_readdir+0x1ca)[0x7f47d40dbc7a]
/usr/lib64/glusterfs/3.4.1/xlator/storage/posix.so(posix_readdirp+0x13)[0x7f47d40dbea3]
/usr/lib64/glusterfs/3.4.1/xlator/features/access-control.so(posix_acl_readdirp+0x19d)[0x7f47cfbf638d]
/usr/lib64/glusterfs/3.4.1/xlator/features/locks.so(pl_readdirp+0x1e7)[0x7f47cf9df817]
/usr/lib64/glusterfs/3.4.1/xlator/performance/io-threads.so(iot_readdirp_wrapper+0x142)[0x7f47cf7c9702]
/usr/lib64/libglusterfs.so.0(call_resume+0x17b)[0x7f47da08d73b]
/usr/lib64/glusterfs/3.4.1/xlator/performance/io-threads.so(iot_worker+0x158)[0x7f47cf7d1ac8]
/lib64/libpthread.so.0(+0x7c6b)[0x7f47d9a1ec6b]
/lib64/libc.so.6(clone+0x6d)[0x7f47d93a95ed]

-----------------------------------

Cloud you please let me know a source of the problem or any ideas if
you have something?

Thank you very much.



More information about the Gluster-users mailing list