Bug 762890 (GLUSTER-1158)

Summary: 2.0.x clients seem to crash 3.0.5
Product: [Community] GlusterFS Reporter: Chida <chida>
Component: coreAssignee: Anand Avati <aavati>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: urgent    
Version: 3.0.5CC: chida, chrisw, gluster-bugs, joe, tejas
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chida 2010-07-16 17:10:05 UTC
A key customer reported segfaults when 2.0.1 and 2.0.7 clients attempting to
connect to the 3.0.5 server.

Client version checks on the server should have stopped the client before causing the segfault.

This was reproduced on another volume though it didn't show any
attempted connections in the debug output:

[2010-07-15 02:20:52] D [glusterfsd.c:432:_get_specfp] glusterfs:
loading volume file /etc/glusterfs/glusterfsd.vol
[2010-07-15 02:20:52] D [xlator.c:745:xlator_set_type] xlator:
dlsym(notify) on
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/xlator/features/posix-locks.so:
undefined symbol: notify -- neglecting
[2010-07-15 02:20:52] D [xlator.c:745:xlator_set_type] xlator:
dlsym(notify) on
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/xlator/performance/io-threads.so:
undefined symbol: notify -- neglecting
[2010-07-15 02:20:52] D [xlator.c:750:xlator_set_type] xlator:
dlsym(dumpops) on
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/xlator/performance/io-threads.so:
undefined symbol: dumpops -- neglecting
================================================================================
Version : glusterfs 3.0.5 built on Jul 9 2010 12:37:24
git: v3.0.5
Starting Time: 2010-07-15 02:20:52
Command line : /usr/local/glusterfs-3.0.5/sbin/glusterfsd -p
/var/run/glusterfsd.pid -f /etc/glusterfs/glusterfsd.vol
--log-file=/var/log/glusterfs/glusterfsd.log --debug
PID : 12992
System name : Linux
Nodename : nwtnhqfarm02.iowatelecom.net
Kernel Release : 2.6.26.6-r710-050109
Hardware Identifier: x86_64

Given volfile:
+------------------------------------------------------------------------------+
1:
2: volume brick02-posix
3: type storage/posix
4: option directory /media/sda3/brick-02
5: end-volume
6:
7:
8: volume brick02-posix-locks
9: type features/posix-locks
10: subvolumes brick02-posix
11: end-volume
12:
13:
14: volume brick02
15: type performance/io-threads
16: option thread-count 4
17: # option thread-count 16
18: subvolumes brick02-posix-locks
19: end-volume
20:
21:
22: ### Add network serving capability to above brick.
23: volume server
24: type protocol/server
25: option transport-type tcp/server # For TCP/IP transport
26: option auth.addr.brick02.allow 127.0.0.1,192.168.*
27: option transport.socket.nodelay on
28: option volume-filename.5s02 /etc/glusterfs/glusterfs-client5s02.vol
29: subvolumes brick02
30: end-volume

+------------------------------------------------------------------------------+
[2010-07-15 02:20:52] D [glusterfsd.c:1383:main] glusterfs: running in
pid 12992
[2010-07-15 02:20:52] D [transport.c:123:transport_load] transport:
attempt to load file
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/transport/socket.so
[2010-07-15 02:20:52] D [name.c:556:server_fill_address_family] server:
option address-family not specified, defaulting to inet/inet6
[2010-07-15 02:20:52] D [io-threads.c:2841:init] brick02: io-threads:
Autoscaling: off, min_threads: 4, max_threads: 4
[2010-07-15 02:20:52] N [glusterfsd.c:1409:main] glusterfs: Successfully
started
pending frames:
frame : type(2) op(SETVOLUME)

patchset: v3.0.5
signal received: 11
time of crash: 2010-07-15 02:20:52
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.0.5
/lib/libc.so.6[0x7fc54f09df60]
/usr/local/glusterfs-3.0.5/lib/libglusterfs.so.0(dict_unserialize+0x11f)[0x7fc54f7ef80f]
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/xlator/protocol/server.so(mop_setvolume+0x95)[0x7fc54e023d65]
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/xlator/protocol/server.so(protocol_server_pollin+0x9a)[0x7fc54e01a9da]
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/xlator/protocol/server.so(notify+0x8b)[0x7fc54e01aa6b]
/usr/local/glusterfs-3.0.5/lib/libglusterfs.so.0(xlator_notify+0x43)[0x7fc54f7f4483]
/usr/local/glusterfs-3.0.5/lib/glusterfs/3.0.5/transport/socket.so(socket_event_handler+0xe0)[0x7fc54de0ba00]
/usr/local/glusterfs-3.0.5/lib/libglusterfs.so.0[0x7fc54f80ee0f]
/usr/local/glusterfs-3.0.5/sbin/glusterfsd(main+0x8cd)[0x4044cd]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7fc54f08a1a6]
/usr/local/glusterfs-3.0.5/sbin/glusterfsd[0x402a09]
---------
Segmentation fault (core dumped)

Comment 1 Joe Julian 2010-08-01 15:44:39 UTC

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