Filipe, This bug was fixed a couple of weeks back. Please use 2.0.0rc1 release which has this fix. avati >> (gdb) bt >> #0 0x0000000000000000 in ?? () >> #1 0x00002b4a1b4f7fdd in protocol_client_xfer (frame=0x1ac43920, >> this=0x1ab84fa0, type=1, op=39, >> hdr=<value optimized out>, hdrlen=46, vector=0x0, count=0, >> refs=0x0) at client-protocol.c:476 >> #2 0x00002b4a1b4f89d4 in client_checksum (frame=0x1ac43920, >> this=0x1ab84fa0, loc=0x1ac427e8, >> flag=0) at client-protocol.c:5470 >> #3 0x00002b4a1b716473 in zr_unify_self_heal (frame=0x1ac416b0, >> this=<value optimized out>, >> local=0x1ac41700) at unify-self-heal.c:1198 >> #4 0x00002b4a1b7154f8 in unify_lookup_cbk (frame=0x1ac416b0, >> cookie=<value optimized out>, >> this=0x1ab85720, op_ret=0, op_errno=22, inode=0x1ab932f0, >> buf=0x7fff8f87b8d0, dict=0x0) >> at unify.c:524 >> #5 0x00002b4a1b500730 in client_lookup_cbk (frame=0x1ac41d70, hdr=0x1ac424a0, >> hdrlen=<value optimized out>, buf=<value optimized out>, >> buflen=<value optimized out>) >> at client-protocol.c:4814 >> #6 0x00002b4a1b4f1fe1 in protocol_client_pollin (this=0x1ab85360, >> trans=0x1ab8ee50) >> at client-protocol.c:6206 >> #7 0x00002b4a1b4f84ba in notify (this=0x1ab85360, event=2, data=0x1ab8ee50) >> at client-protocol.c:6246 >> #8 0x00002aaaaaaadd5e in socket_event_handler (fd=<value optimized out>, >> idx=<value optimized out>, data=0x1ab8ee50, poll_in=112, >> poll_out=<value optimized out>, >> poll_err=0) at socket.c:678 >> #9 0x00002b4a1b269a65 in event_dispatch_epoll (event_pool=0x1ab7f230) >> at event.c:804 >> #10 0x00000000004032e9 in main (argc=5, argv=0x7fff8f87c7e8) at >> glusterfsd.c:1068
