Re: [Gluster-devel] Multiple NFS Servers (Gluster NFS in 3.x, unfsd, knfsd, etc.)

[Anand Avati]

> [2010-01-06 21:35:54] N [server-protocol.c:7065:mop_setvolume] server-home:
> accepted client from 10.2.3.1:1023
> [2010-01-06 21:35:54] N [server-protocol.c:7065:mop_setvolume] server-home:
> accepted client from 10.2.3.1:1022
> pending frames:
> frame : type(1) op(LOOKUP)
> frame : type(1) op(LK)
>
> patchset: v2.0.9
> signal received: 11
> time of crash: 2010-01-06 21:36:12
> configuration details:
> argp 1
> backtrace 1
> db.h 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.9
> /lib64/libc.so.6[0x3f55e302d0]
> /usr/lib64/glusterfs/2.0.9/xlator/protocol/client.so(client_lookup+0xc8)[0x2afea8f89438]
> /usr/lib64/glusterfs/2.0.9/xlator/cluster/replicate.so(afr_lookup+0x226)[0x2afea97e3e66]
> /usr/lib64/glusterfs/2.0.9/xlator/protocol/server.so(server_lookup_cbk+0x513)[0x2afea95cb2a3]
> /usr/lib64/glusterfs/2.0.9/xlator/cluster/replicate.so(afr_self_heal_cbk+0x8e)[0x2afea97e46fe]
> /usr/lib64/glusterfs/2.0.9/xlator/cluster/replicate.so(afr_sh_data_done+0xbe)[0x2afea97f8bce]
> /usr/lib64/glusterfs/2.0.9/xlator/cluster/replicate.so(afr_sh_data_flush_cbk+0x44)[0x2afea97fa284]
> /usr/lib64/glusterfs/2.0.9/xlator/cluster/replicate.so(afr_sh_data_utimes_cbk+0x9)[0x2afea97fa2a9]
> /usr/lib64/glusterfs/2.0.9/xlator/protocol/client.so(client_utimens_cbk+0x14e)[0x2afea8f9152e]
> /usr/lib64/glusterfs/2.0.9/xlator/protocol/client.so(protocol_client_pollin+0xca)[0x2afea8f808aa]
> /usr/lib64/glusterfs/2.0.9/xlator/protocol/client.so(notify+0x212)[0x2afea8f874e2]
> /usr/lib64/glusterfs/2.0.9/transport/socket.so(socket_event_handler+0xd3)[0x2aaaaaaafe33]
> /usr/lib64/libglusterfs.so.0[0x3f56a27115]
> /usr/sbin/glusterfs(main+0xa06)[0x403e96]
> /lib64/libc.so.6(__libc_start_main+0xf4)[0x3f55e1d994]
> /usr/sbin/glusterfs[0x402509]
> ---------

Can you send us a 'apply thread all bt full' from this core? This
might be a bug which we fixed in 3.0 but have missed applying the
patch in 2.0 tree. The backtrace can help us here.

Avati