[Bugs] [Bug 1218553] [Bitrot]: glusterd crashed when node was rebooted

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1218553



--- Comment #2 from senaik at redhat.com ---
Version :
=======
gluster --version
glusterfs 3.7.0beta1 built on May  1 2015

Faced a similar crash while attaching another node to the cluster where volumes
had bit rot enabled.

[root at inception ~]# gluster peer probe  snapshot11.lab.eng.blr.redhat.com
peer probe: failed: Probe returned with unknown errno -1


(gdb) bt
#0  0x00007f750ca2a4c6 in glusterd_bitdsvc_manager () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#1  0x00007f750ca28bed in glusterd_svcs_manager () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#2  0x00007f750c99e6f2 in glusterd_compare_friend_data () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#3  0x00007f750c9759f3 in ?? () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#4  0x00007f750c9766e0 in glusterd_friend_sm () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#5  0x00007f750c974ad2 in __glusterd_handle_incoming_friend_req () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#6  0x00007f750c95bebf in glusterd_big_locked_handler () from
/usr/lib64/glusterfs/3.7.0beta1/xlator/mgmt/glusterd.so
#7  0x00000031f6c09c85 in rpcsvc_handle_rpc_call () from
/usr/lib64/libgfrpc.so.0
#8  0x00000031f6c09ec3 in rpcsvc_notify () from /usr/lib64/libgfrpc.so.0
#9  0x00000031f6c0b7b8 in rpc_transport_notify () from /usr/lib64/libgfrpc.so.0
#10 0x00007f750bbd9bcd in ?? () from
/usr/lib64/glusterfs/3.7.0beta1/rpc-transport/socket.so
#11 0x00007f750bbdb6fd in ?? () from
/usr/lib64/glusterfs/3.7.0beta1/rpc-transport/socket.so
#12 0x00000031f647d4b0 in ?? () from /usr/lib64/libglusterfs.so.0
#13 0x00000032284079d1 in start_thread () from /lib64/libpthread.so.0
#14 0x00000032280e88fd in clone () from /lib64/libc.so.6

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.