[Bugs] [Bug 1197631] glusterd crashed after peer probe

bugzilla at redhat.com bugzilla at redhat.com
Mon Mar 9 08:20:25 UTC 2015


--- Comment #3 from Anand Nekkunti <anekkunt at redhat.com> ---
Above link for rpm is 8 Feb 2015  but glusterd version showing 01 Mar 2015  
[root at vertigo /]# gluster --version
glusterfs 3.7dev built on Mar  1 2015 01:03:38 

rpms for 01-mar-2015 is : 

Back trace  from core dump :

Loaded symbols for /lib64/libnss_dns-2.12.so
Core was generated by `/usr/sbin/glusterd --pid-file=/var/run/glusterd.pid'.
Program terminated with signal 7, Bus error.
#0  __gf_free (free_ptr=0x7fb4c8000d90) at mem-pool.c:261
261            if (!xl->mem_acct.rec) {
(gdb) bt
#0  __gf_free (free_ptr=0x7fb4c8000d90) at mem-pool.c:261
#1  0x00007fb4e31553a5 in data_destroy (data=0x7fb4e180fbe0) at dict.c:148
#2  0x00007fb4e315561e in dict_get_str (this=<value optimized out>, key=<value
optimized out>, str=0x7fb4c4203178) at dict.c:2097
#3  0x00007fb4d8e7465a in glusterd_xfer_cli_probe_resp (req=0x19fe35c,
op_ret=-1, op_errno=0, op_errstr=0x0, hostname=0x7fb4c8000d50 "", port=24007,
dict=0x7fb4e19f1538) at glusterd-handler.c:3455
#4  0x00007fb4d8e75442 in __glusterd_handle_cli_probe (req=0x19fe35c) at
#5  0x00007fb4d8e6064f in glusterd_big_locked_handler (req=0x19fe35c,
actor_fn=0x7fb4d8e75090 <__glusterd_handle_cli_probe>) at glusterd-handler.c:82
#6  0x00007fb4e3199502 in synctask_wrap (old_task=<value optimized out>) at
#7  0x0000003a38c438f0 in ?? () from /lib64/libc-2.12.so
#8  0x0000000000000000 in ?? ()
(gdb) list 
256            memcpy (&xl, ptr, sizeof(xlator_t *));
258            //gf_free expects xl to be available
259            GF_ASSERT (xl != NULL);
261            if (!xl->mem_acct.rec) {
262                    ptr = (char *)free_ptr - GF_MEM_HEADER_SIZE;
263                    goto free;
264            }

 I am not able to reproduce this bug as mention above steps, 
Please can explain when it happen or can you reproduce it , Based on 
core and sos report  I found that glusterd was killed  due to SIGBUS 
while accessing the dictionary . I am not able to figure out what could 
be the problem ,but  I found it is happen due to memory  alignment issue 
, not related to peer probe .

As per discussed with Bhaskar , It is happening one time during nfs related
https://bugzilla.redhat.com/show_bug.cgi?id=1196546) .

Need more info to analyse this bug ..........

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=QNi7l2sc5b&a=cc_unsubscribe

More information about the Bugs mailing list