Hide Forgot
[2010-07-29 15:43:41] E [client-protocol.c:313:call_bail] be02g-2: bailing out frame LK(26) frame sent = 2010-07- 29 15:13:39. frame-timeout = 1800 pending frames: frame : type(1) op(LK) patchset: v3.0.5 signal received: 11 time of crash: 2010-07-29 15:43:41 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 /lib64/libc.so.6[0x7fa41b35a560] /usr/lib64/glusterfs/3.0.5/xlator/protocol/client.so(client_lk_common_cbk+0xee)[0x7fa41a9059ae] /usr/lib64/glusterfs/3.0.5/xlator/protocol/client.so[0x7fa41a90a725] /usr/lib64/libglusterfs.so.0(gf_timer_proc+0xac)[0x7fa41bac5d7c] /lib64/libpthread.so.0[0x7fa41b68965d] /lib64/libc.so.6(clone+0x6d)[0x7fa41b3f8e1d] backtrace--- Loaded symbols for /lib64/libgcc_s.so.1 Core was generated by `/usr/sbin/glusterfs --log-level=NORMAL --volfile=/etc/glusterfs/mod-dist-repl.v'. Program terminated with signal 11, Segmentation fault. #0 0x00007fa41a9059ae in client_lk_common_cbk (frame=0x623660, hdr=<value optimized out>, hdrlen=<value optimized out>, iobuf=<value optimized out>) at client-protocol.c:5416 5416 client-protocol.c: No such file or directory. in client-protocol.c (gdb) bt #0 0x00007fa41a9059ae in client_lk_common_cbk (frame=0x623660, hdr=<value optimized out>, hdrlen=<value optimized out>, iobuf=<value optimized out>) at client-protocol.c:5416 #1 0x00007fa41a90a725 in call_bail (data=<value optimized out>) at client-protocol.c:320 #2 0x00007fa41bac5d7c in gf_timer_proc (ctx=0x609010) at timer.c:172 #3 0x00007fa41b68965d in start_thread () from /lib64/libpthread.so.0 #4 0x00007fa41b3f8e1d in clone () from /lib64/libc.so.6 #5 0x0000000000000000 in ?? ()
PATCH: http://patches.gluster.com/patch/4008 in master (fix rpm spec file to build rpms for 3.1)
What is this going on 1251 patch was supposed to be something else? .. there is a necessity for the patches against the bug id to be coherent. RPM spec 3.1 doesn't come as a fix for this.
Harsha, Are you still seeing this bug? the protocol itself is completely different now..
Pavan, can you confirm this is addressed in 3.1.x code? if not lets get it tested and see.
(In reply to comment #4) > Pavan, can you confirm this is addressed in 3.1.x code? if not lets get it > tested and see. Amar this issue is due to ping_pong locks when ran on same system, it is perfect for it to hang since its a deadlock, this is too see if glusterfs detects a ping_pong deadlock. But this deadlock times-out after 1800secs resulting in a crash in client_lk_common_cbk. Since reproducing this is simple and easy shouldn't take much longer than 1hr.
Johny, Can you try to see if this issue happens on 3.1.x release, and if not, can you close the ticket?
Not happening consistently.
Please update the status of this bug as its been more than 6months since its filed (bug id < 2000) Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.
(In reply to comment #8) > Please update the status of this bug as its been more than 6months since its > filed (bug id < 2000) > > Please resolve it with proper resolution if its not valid anymore. If its still > valid and not critical, move it to 'enhancement' severity. This was during the problems with locking translator. Posix-locks didn't have lock upgrade and downgrade. Since CTDB works with Gluster, i believe this can be closed for now. Reopen as a new bug if there are problems.