[Bugs] [Bug 1341942] New: glusterd coredump due to assert failed with GF_ASSERT ( GD_OP_HEAL_VOLUME == op)

[bugzilla at redhat.com]

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

            Bug ID: 1341942
           Summary: glusterd coredump due to assert failed with
                    GF_ASSERT (GD_OP_HEAL_VOLUME == op)
           Product: GlusterFS
           Version: 3.6.9
         Component: glusterd
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: george.lian at nokia.com
                CC: bugs at gluster.org



Description of problem:
glusterd failed with coredump when assert failed

Version-Release number of selected component (if applicable):


How reproducible:
loop running CLI command gluster volume heal ...

Steps to Reproduce:
1.
2.
3.

Actual results: coredump trace as the below:
(gdb) bt
#0  0x00007f3abd94b177 in __GI_raise (sig=sig at entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x00007f3abd94c5fa in __GI_abort () at abort.c:89
#2  0x00007f3abd94415d in __assert_fail_base (fmt=0x7f3abda7b768 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n",
    assertion=assertion at entry=0x7f3aba3345c0 "GD_OP_HEAL_VOLUME == op",
file=file at entry=0x7f3aba32fc02 "glusterd-utils.c", line=line at entry=10921,
    function=function at entry=0x7f3aba338120 "glusterd_volume_heal_use_rsp_dict")
at assert.c:92
#3  0x00007f3abd944212 in __GI___assert_fail (assertion=0x7f3aba3345c0
"GD_OP_HEAL_VOLUME == op", file=0x7f3aba32fc02 "glusterd-utils.c", line=10921,
    function=0x7f3aba338120 "glusterd_volume_heal_use_rsp_dict") at
assert.c:101
#4  0x00007f3aba295e30 in glusterd_volume_heal_use_rsp_dict () from
/usr/lib64/glusterfs/3.6.9/xlator/mgmt/glusterd.so
#5  0x00007f3aba2f651f in glusterd_syncop_aggr_rsp_dict () from
/usr/lib64/glusterfs/3.6.9/xlator/mgmt/glusterd.so
#6  0x00007f3aba2f7e9c in _gd_syncop_commit_op_cbk () from
/usr/lib64/glusterfs/3.6.9/xlator/mgmt/glusterd.so
#7  0x00007f3aba29f3a8 in glusterd_big_locked_cbk () from
/usr/lib64/glusterfs/3.6.9/xlator/mgmt/glusterd.so
#8  0x00007f3aba2f7fac in gd_syncop_commit_op_cbk () from
/usr/lib64/glusterfs/3.6.9/xlator/mgmt/glusterd.so
#9  0x00007f3abe75d6a0 in rpc_clnt_handle_reply () from
/usr/lib64/libgfrpc.so.0
#10 0x00007f3abe75d914 in rpc_clnt_notify () from /usr/lib64/libgfrpc.so.0
#11 0x00007f3abe75a073 in rpc_transport_notify () from /usr/lib64/libgfrpc.so.0
#12 0x00007f3ab952b89e in ?? () from
/usr/lib64/glusterfs/3.6.9/rpc-transport/socket.so
#13 0x00007f3ab952dc58 in ?? () from
/usr/lib64/glusterfs/3.6.9/rpc-transport/socket.so
#14 0x00007f3abe9da9f9 in ?? () from /usr/lib64/libglusterfs.so.0
#15 0x0000000000405288 in main ()


Expected results:


Additional info:
root cause draft investigate:
is global variable opinfo.op cleared by another thread?  seems no lock when
access opinfo? or get opinfo not from global variable but get from
transaction?(through API glusterd_get_txn_opinfo?)

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