Bug 763671 (GLUSTER-1939) - glusterfsd crashing when client is attaching
Summary: glusterfsd crashing when client is attaching
Keywords:
Status: CLOSED DUPLICATE of bug 763666
Alias: GLUSTER-1939
Product: GlusterFS
Classification: Community
Component: core
Version: 3.1.0
Hardware: All
OS: Windows
low
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-12 22:24 UTC by James Devine
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description James Devine 2010-10-12 22:24:14 UTC
I have 3 test machines running ubuntu 10.10 and glusterfs 3.1.0.  I created a 2 node replicated volume and when I try to connect the client, it connects but it causes glusterfsd on one of the bricks to crash.  /usr/local/var/log/glusterfs/bricks/export.log on the brick that crashes shows:


[2010-10-12 15:41:49.638228] I [server-handshake.c:535:server_setvolume] testvol-server: accepted client from 10.10.10.82:1020
pending frames:

patchset: v3.1.0
signal received: 11
time of crash: 2010-10-12 15:42:01
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.1.0
/lib/libc.so.6(+0x33c20)[0x7fa5a72bfc20]
/usr/lib/glusterfs/3.1.0/xlator/storage/posix.so(posix_getxattr+0x13b)[0x7fa5a4865aab]
/usr/lib/libglusterfs.so.0(default_getxattr+0xdd)[0x7fa5a7e77c5d]

Comment 1 Amar Tumballi 2010-10-13 02:32:11 UTC
Crash backtrace is similar to bug 763666, and the fix is also same for both.

*** This bug has been marked as a duplicate of bug 1934 ***


Note You need to log in before you can comment on or make changes to this bug.