In 3.3.0 I'm crashing out of the client (segfault) in fuse_thread_proc on Fedora 17. This started happening after booting to kernel 3.5.2-3.fc17.x86_64. (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x00007effec4dd5c1 in fuse_thread_proc (data=0xbb0030) at fuse-bridge.c:4072 mount_point = 0x0 this = 0xbb0030 priv = 0xbb0e90 res = 72 iobuf = 0xbaeb20 finh = <optimized out> iov_in = {{iov_base = 0x7effdc04ad20, iov_len = 80}, {iov_base = 0x7effed1ec000, iov_len = 131072}} msg = <optimized out> fuse_ops = 0x7effec6e7f60 pfd = {{fd = 5, events = 25, revents = 1}, {fd = 7, events = 25, revents = 1}} mount_finished = _gf_true __FUNCTION__ = "fuse_thread_proc" #2 0x0000003ea4607d14 in start_thread (arg=0x7effe1f38700) at pthread_create.c:309 __res = <optimized out> pd = 0x7effe1f38700 now = <optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139637472593664, -7166573178386444316, 0, 269031178240, 139637472593664, 24, 7022506330125438948, -7136376462306635804}, mask_was_saved = 0}}, priv = { pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = 0 pagesize_m1 = <optimized out> sp = <optimized out> freesize = <optimized out> #3 0x0000003ea3af167d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 No locals.
I confirmed that rolling back to 3.3.7-1.fc16.x86_64 prevents this crash.
I just gave 3.3.0 a quick whirl on F17 and didn't reproduce a crash with basic I/O. BTW, my updated F17 is at kernel 3.5.3-1. yumdownloader doesn't give me anything for a 3.5.2-3 kernel... I don't know what operations you're doing to reproduce this, but I can reproduce a crash with an fallocate command (bug 856704). Given the source of this crash (fuse-bridge.c:4072), I suspect this issue could be related. You might want kkeithley's fix from said bug: 2564ab2bc8cd3aa2561e091f72278e480fcef33d
doesn't seem to be an issue with latest 3.3 branch, or 3.4.x releases.
*** Bug 852224 has been marked as a duplicate of this bug. ***
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed.