Bug 762002 (GLUSTER-270)

Summary: glusterfsd crashed with segfault
Product: [Community] GlusterFS Reporter: Andreas Hauser <hauser>
Component: coreAssignee: Anand Avati <aavati>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 2.0.6CC: chrisw, gluster-bugs, vijay
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: Type: ---
Regression: RTP Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
glusterfsd.vol
none
glusterfs-client.vol none

Description Andreas Hauser 2009-09-17 12:42:01 UTC 
Created attachment 72 [details]
Diff against texinfo-4.0-2 spec-file
Comment 1 Vijay Bellur 2009-09-17 14:51:20 UTC 
(In reply to comment #1)
Hi Andreas,

Thanks for reporting this. The backtrace looks like the same as in bug 761947. Can you please confirm if patch 1292 (http://patches.gluster.com/patch/1292) fixes this crash?

Thanks.
Comment 2 Andreas Hauser 2009-09-17 15:41:20 UTC 
Glusterfsd crashed with segfault in a simple NFS-like setup, see log:

pending frames:
frame : type(1) op(LOOKUP)
frame : type(1) op(LINK)
frame : type(1) op(LINK)

patchset: v2.0.6
signal received: 11
time of crash: 2009-09-14 04:06:45
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.6
/lib64/libc.so.6[0x3318a30280]
/usr/lib64/libglusterfs.so.0(inode_ref+0xe)[0x2acd5a40b19e]
/usr/lib64/glusterfs/2.0.6/xlator/protocol/server.so(server_link_resume+0x1a1)[0x2acd5b4cd7b1]
/usr/lib64/libglusterfs.so.0(call_resume+0x581)[0x2acd5a40cc31]
/usr/lib64/glusterfs/2.0.6/xlator/protocol/server.so(server_stub_resume+0x32)[0x2acd5b4db472]
/usr/lib64/glusterfs/2.0.6/xlator/protocol/server.so[0x2acd5b4dd412]
/usr/lib64/glusterfs/2.0.6/xlator/performance/io-threads.so(iot_lookup_cbk+0x34)[0x2acd5b2bb664]
/usr/lib64/libglusterfs.so.0[0x2acd5a4030e4]
/usr/lib64/glusterfs/2.0.6/xlator/storage/posix.so(posix_lookup+0x2e4)[0x2acd5aea2da4]
/usr/lib64/libglusterfs.so.0(default_lookup+0xb5)[0x2acd5a406605]
/usr/lib64/glusterfs/2.0.6/xlator/performance/io-threads.so(iot_lookup_wrapper+0xb5)[0x2acd5b2bea95]
/usr/lib64/libglusterfs.so.0(call_resume+0x316)[0x2acd5a40c9c6]
/usr/lib64/glusterfs/2.0.6/xlator/performance/io-threads.so(iot_worker_unordered+0xe)[0x2acd5b2bc73e]
/lib64/libpthread.so.0[0x3319606367]
/lib64/libc.so.6(clone+0x6d)[0x3318ad2f7d]
---------
Comment 3 Andreas Hauser 2009-09-28 07:54:14 UTC 
(Mit Bezug zu comment #2)
> (In reply to comment #1)
> Hi Andreas,
> 
> Thanks for reporting this. The backtrace looks like the same as in bug 761947. Can
> you please confirm if patch 1292 (http://patches.gluster.com/patch/1292) fixes
> this crash?
> 
> Thanks.

With the patch it's been up longer than before now.