[Gluster-users] gluster client crash
Mingfan Lu
mingfan.lu at gmail.com
Mon Jan 27 10:31:56 UTC 2014
sorry, our customer remounted, so it is possible to get the full backtrace.
the full version is glusterfs-3.3.0.5rhs_iqiyi_6-1.el6.x86_64
it is a self-built version.
The code started from this change.
%changelog
* Wed May 9 2012 Kaleb S. KEITHLEY <kkeithle[at]redhat.com>
- Add BuildRequires: libxml2-devel so that configure will DTRT on for
- Fedora's Koji build system
with some backports:
1. backport patch to avoid fd leek during rebalance see
http://review.gluster.org/4888
2. backport http://review.gluster.org/#/c/4459/ to avoid gfid mismatch
during concurrent mkdir
On Mon, Jan 27, 2014 at 6:04 PM, Vijay Bellur <vbellur at redhat.com> wrote:
> On 01/27/2014 01:34 PM, Mingfan Lu wrote:
>
>> the volume is distributed (replication = 1)
>>
>
> Is it possible to obtain a full backtrace using gdb?
>
> Also, what is the complete version string of this glusterfs release?
>
> Thanks,
> Vijay
>
>
>>
>> On Mon, Jan 27, 2014 at 4:01 PM, Mingfan Lu <mingfan.lu at gmail.com
>> <mailto:mingfan.lu at gmail.com>> wrote:
>>
>> One of our client (3.3.0.5) crashed when writing data, the log is:
>>
>> pending frames:
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(LOOKUP)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(READ)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> frame : type(1) op(WRITE)
>> patchset: git://git.gluster.com/glusterfs.git
>> <http://git.gluster.com/glusterfs.git>
>> signal received: 6
>> time of crash: 2014-01-27 15:36:32
>> 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 3.3.0.5rhs
>> /lib64/libc.so.6[0x32c5a32920]
>> /lib64/libc.so.6(gsignal+0x35)[0x32c5a328a5]
>> /lib64/libc.so.6(abort+0x175)[0x32c5a34085]
>> /lib64/libc.so.6[0x32c5a707b7]
>> /lib64/libc.so.6[0x32c5a760e6]
>> /usr/lib64/glusterfs/3.3.0.5rhs/xlator/performance/write-
>> behind.so(+0x42be)[0x7f79a63012be]
>> /usr/lib64/glusterfs/3.3.0.5rhs/xlator/performance/write-
>> behind.so(wb_sync_cbk+0xa0)[0x7f79a6307ab0]
>> /usr/lib64/glusterfs/3.3.0.5rhs/xlator/features/quota.so(
>> quota_writev_cbk+0xed)[0x7f79a651864d]
>> /usr/lib64/glusterfs/3.3.0.5rhs/xlator/cluster/
>> distribute.so(dht_writev_cbk+0x14f)[0x7f79a6753aaf]
>> /usr/lib64/glusterfs/3.3.0.5rhs/xlator/protocol/client.
>> so(client3_1_writev_cbk+0x600)[0x7f79a6995340]
>> /usr/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0xa5)[0x31b020f4f5]
>> /usr/lib64/libgfrpc.so.0(rpc_clnt_notify+0x120)[0x31b020fdb0]
>> /usr/lib64/libgfrpc.so.0(rpc_transport_notify+0x28)[0x31b020aeb8]
>> /usr/lib64/glusterfs/3.3.0.5rhs/rpc-transport/socket.so(
>> socket_event_poll_in+0x34)[0x7f79a79d4784]
>> /usr/lib64/glusterfs/3.3.0.5rhs/rpc-transport/socket.so(
>> socket_event_handler+0xc7)[0x7f79a79d4867]
>> /usr/lib64/libglusterfs.so.0[0x31afe3e4e4]
>> /usr/sbin/glusterfs(main+0x590)[0x407420]
>> /lib64/libc.so.6(__libc_start_main+0xfd)[0x32c5a1ecdd]
>> /usr/sbin/glusterfs[0x404289]
>>
>>
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140127/659764c3/attachment.html>
More information about the Gluster-users
mailing list