Bug 1183962

Summary: 3.6.0.29-2.el6 glusterfs client crash
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Patryk Bator <patryk.bator>
Component: coreAssignee: Vijay Bellur <vbellur>
Status: CLOSED CURRENTRELEASE QA Contact: storage-qa-internal <storage-qa-internal>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.0CC: nbalacha, patryk.bator, rhs-bugs, storage-qa-internal, vagarwal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-27 06:53:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Patryk Bator 2015-01-20 10:06:28 UTC
Description of problem:
After few minutes following glusterfs client crash when production traffic on host is turn on. Coredump is creating.
When I'm using glusterfs3.4.0.57 client everything works fine.
Glusterfs server is on 3.6.0.29-2.el6 version


Version-Release number of selected component (if applicable):
glusterfs 3.6.0.29-2.el6 

How reproducible:
Always

Steps to Reproduce:
1. mount gluster resource using client 3.6.0.29-2
2. turn on prodution traffic on host with apache server
3. after 1-2 minutes glusterfs resource was automatically unmounted, glusterfs client crash, coredump is creating


Actual results:
Always after few minutes glusterfs crash, remote resource are not available

Expected results:
Stop crashing on gluster3.6.0.29 client


Additional info:

Core was generated by `/usr/sbin/glusterfs --log-level=DEBUG --volfile-server=mount.gluster --vol'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f8c70b42c03 in dht_lookup_everywhere_done ()
   from /usr/lib64/glusterfs/3.6.0.29/xlator/cluster/distribute.so
(gdb) bt
#0  0x00007f8c70b42c03 in dht_lookup_everywhere_done ()
   from /usr/lib64/glusterfs/3.6.0.29/xlator/cluster/distribute.so
#1  0x00007f8c70b475c3 in dht_lookup_everywhere_cbk ()
   from /usr/lib64/glusterfs/3.6.0.29/xlator/cluster/distribute.so
#2  0x00007f8c70dcab18 in afr_lookup_cbk ()
   from /usr/lib64/glusterfs/3.6.0.29/xlator/cluster/replicate.so
#3  0x00007f8c71009267 in client3_3_lookup_cbk ()
   from /usr/lib64/glusterfs/3.6.0.29/xlator/protocol/client.so
#4  0x00007f8c7b89d9c5 in rpc_clnt_handle_reply () from /usr/lib64/libgfrpc.so.0
#5  0x00007f8c7b89ee4f in rpc_clnt_notify () from /usr/lib64/libgfrpc.so.0
#6  0x00007f8c7b89a668 in rpc_transport_notify () from /usr/lib64/libgfrpc.so.0
#7  0x00007f8c71649275 in socket_event_poll_in (this=0xb94e30) at socket.c:2127
#8  0x00007f8c7164ac5d in socket_event_handler (fd=<value optimized out>, 
    idx=<value optimized out>, data=0xb94e30, poll_in=1, poll_out=0, poll_err=0) at socket.c:2240
#9  0x00007f8c7bb1f367 in ?? () from /usr/lib64/libglusterfs.so.0
#10 0x0000000000407e93 in main ()

/var/log/messages ->

pending frames:
frame : type(1) op(LOOKUP)
frame : type(1) op(LOOKUP)
frame : type(0) op(0)
patchset: git://git.gluster.com/glusterfs.git
signal received: 11
time of crash: 
2015-01-19 13:36:59
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.6.0.29
---------

Comment 3 Vivek Agarwal 2015-04-22 06:34:12 UTC
Patryk, seems this is already fixed.Can you confirm.

Comment 4 Patryk Bator 2015-04-27 06:53:56 UTC
Yes, this problem is fixed in glusterfs 3.6.0.53 version. Thank you.