<font size=2 face="sans-serif">Thanks for your reponse.</font>
<br>
<br><font size=2 face="sans-serif">Our glibc is:</font>
<br>
<br><font size=2 face="sans-serif">[root@host-247 glusterfs]# rpm -qa |
grep glibc</font>
<br><font size=2 face="sans-serif">glibc-common-2.17-55.el7.x86_64</font>
<br><font size=2 face="sans-serif">glibc-devel-2.17-55.el7.i686</font>
<br><font size=2 face="sans-serif">glibc-2.17-55.el7.x86_64</font>
<br><font size=2 face="sans-serif">glibc-static-2.17-55.el7.x86_64</font>
<br><font size=2 face="sans-serif">compat-glibc-headers-2.12-4.el7.x86_64</font>
<br><font size=2 face="sans-serif">glibc-headers-2.17-55.el7.x86_64</font>
<br><font size=2 face="sans-serif">glibc-devel-2.17-55.el7.x86_64</font>
<br><font size=2 face="sans-serif">glibc-2.17-55.el7.i686</font>
<br><font size=2 face="sans-serif">compat-glibc-2.12-4.el7.x86_64<br>
</font>
<br>
<br>
<br>
<br>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
<br>
----- Original Message -----<br>
> From: "Vijay Bellur" <vbellur@redhat.com><br>
> To: "yang bin18" <yang.bin18@zte.com.cn><br>
> Cc: "Gluster Devel" <gluster-devel@gluster.org><br>
> Sent: Tuesday, April 19, 2016 9:17:42 AM<br>
> Subject: Re: [Gluster-devel] Glusterfs core report.<br>
> <br>
> <br>
> <br>
> On Fri, Apr 15, 2016 at 2:43 AM, yang.bin18@zte.com.cn <<br>
> yang.bin18@zte.com.cn > wrote:<br>
> <br>
> <br>
> Glusterfs core when mounting. here is the backtree.<br>
> <br>
> <br>
> Program terminated with signal 6, Aborted.<br>
> #0 0x00007f308ca04989 in raise () from /lib64/libc.so.6<br>
> Missing separate debuginfos, use: debuginfo-install glibc-2.17-55.el7.x86_64<br>
> keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.11.3-49.el7.x86_64<br>
> libcom_err-1.42.9-4.el7.x86_64 libgcc-4.8.2-16.el7.x86_64<br>
> libselinux-2.2.2-6.el7.x86_64 openssl-libs-1.0.1e-34.el7.7.x86_64<br>
> pcre-8.32-12.el7.x86_64 sssd-client-1.11.2-65.el7.x86_64<br>
> xz-libs-5.1.2-8alpha.el7.x86_64 zlib-1.2.7-13.el7.x86_64<br>
> (gdb) bt<br>
> #0 0x00007f308ca04989 in raise () from /lib64/libc.so.6<br>
> #1 0x00007f308ca06098 in abort () from /lib64/libc.so.6<br>
> #2 0x00007f308ca45197 in __libc_message () from /lib64/libc.so.6<br>
> #3 0x00007f308ca4c56d in _int_free () from /lib64/libc.so.6<br>
> #4 0x00007f308096ebc1 in dht_local_wipe (this=0x7f308f306460,<br>
> local=0x7f3080042880) at dht-helper.c:475<br>
> #5 0x00007f308099b9fd in dht_writev_cbk (frame=0x7f308bc11e5c,<br>
> cookie=<optimized out>, this=<optimized out>, op_ret=131072,<br>
> op_errno=0, prebuf=<optimized out>, postbuf=0x7fff2020c870,
xdata=0x0) at<br>
> dht-inode-write.c:84<br>
> #6 0x00007f3080be4512 in client3_3_writev_cbk (req=<optimized out>,<br>
> iov=<optimized out>, count=<optimized out>,<br>
> myframe=0x7f308bc116f8) at client-rpc-fops.c:856<br>
> #7 0x00007f308d7bd100 in rpc_clnt_handle_reply<br>
> (clnt=clnt@entry=0x7f308f3292d0, pollin=pollin@entry=0x7f308f39bb10)<br>
> at rpc-clnt.c:763<br>
> #8 0x00007f308d7bd374 in rpc_clnt_notify (trans=<optimized out>,<br>
> mydata=0x7f308f329300, event=<optimized out>,<br>
> data=0x7f308f39bb10) at rpc-clnt.c:891<br>
> #9 0x00007f308d7b92c3 in rpc_transport_notify<br>
> (this=this@entry=0x7f308f35f3f0,<br>
> event=event@entry=RPC_TRANSPORT_MSG_RECEIVED,<br>
> data=data@entry=0x7f308f39bb10) at rpc-transport.c:516<br>
> #10 0x00007f3082ac17a0 in socket_event_poll_in<br>
> (this=this@entry=0x7f308f35f3f0) at socket.c:2234<br>
> #11 0x00007f3082ac3f94 in socket_event_handler (fd=<optimized out>,
idx=1,<br>
> data=data@entry=0x7f308f35f3f0, poll_in=1, poll_out=0,<br>
> poll_err=0) at socket.c:2347<br>
> #12 0x00007f308da3e8c2 in event_dispatch_epoll_handler (i=<optimized
out>,<br>
> events=0x7f308f2febd0, event_pool=0x7f308f2b76c0)<br>
> at event-epoll.c:384<br>
> #13 event_dispatch_epoll (event_pool=0x7f308f2b76c0) at event-epoll.c:445<br>
> #14 0x00007f308de92fe2 in main (argc=4, argv=0x7fff2020de78) at<br>
> glusterfsd.c:2060<br>
> <br>
> <br>
> Thanks for the report. What version of gluster is being used here?
I assume<br>
> this is on Centos 7.<br>
<br>
What is the version of glibc? recently we identified a corruption caused
by glibc:<br>
</font></tt><a href="https://bugzilla.redhat.com/show_bug.cgi?id=892601"><tt><font size=2>https://bugzilla.redhat.com/show_bug.cgi?id=892601</font></tt></a><tt><font size=2><br>
<br>
The issue you are seeing might as well be related.<br>
<br>
> <br>
> Would it be possible to share the client log file?<br>
> <br>
> Regards,<br>
> Vijay<br>
> <br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> Gluster-devel@gluster.org<br>
> </font></tt><a href="http://www.gluster.org/mailman/listinfo/gluster-devel"><tt><font size=2>http://www.gluster.org/mailman/listinfo/gluster-devel</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><pre><font color="blue">
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
</font></pre><br>