[Bugs] [Bug 1217589] glusterd crashed while schdeuler was creating snapshots when bit rot was enabled on the volumes
bugzilla at redhat.com
bugzilla at redhat.com
Fri May 15 18:18:07 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1217589
Atin Mukherjee <amukherj at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(amukherj at redhat.c |
|om) |
--- Comment #7 from Atin Mukherjee <amukherj at redhat.com> ---
(In reply to senaik from comment #4)
> Atin,
>
> Reopening as I needed some clarification.
>
> Core 19223 and 23765 are related/tracked by the bug you mentioned above and
> another bug (bug 1207146).
>
> However, the core on 10.70.36.4:
> ==========
> core.24094
>
> seems to be different and the backtrace is different than the other two
> cores. Can you please check that and clarify?
>
> Reposting the backtrace for clarity.
>
> 10.70.36.4:
> ==========
> core.24094
>
> Core was generated by `/usr/sbin/glusterfs -s localhost --volfile-id
> gluster/bitd -p /var/lib/glusterd'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x0000003efac21734 in gf_log_flush () from /usr/lib64/libglusterfs.so.0
> Missing separate debuginfos, use: debuginfo-install
> glusterfs-3.7.0alpha0-0.17.gited96153.el6.x86_64
> (gdb) bt
> #0 0x0000003efac21734 in gf_log_flush () from /usr/lib64/libglusterfs.so.0
> #1 0x0000003efac3d7ed in gf_print_trace () from /usr/lib64/libglusterfs.so.0
> #2 <signal handler called>
> #3 0x00007f6b6400e820 in ?? ()
> #4 0x00007f6b7cb5cc0a in gf_changelog_reborp_rpcsvc_notify ()
> from /usr/lib64/libgfchangelog.so.0
> #5 0x0000003efb408425 in rpcsvc_handle_disconnect ()
> from /usr/lib64/libgfrpc.so.0
> #6 0x0000003efb409f60 in rpcsvc_notify () from /usr/lib64/libgfrpc.so.0
> #7 0x0000003efb40b7b8 in rpc_transport_notify () from
> /usr/lib64/libgfrpc.so.0
> #8 0x00007f6b7ddd86a1 in ?? ()
> from /usr/lib64/glusterfs/3.7.0alpha0/rpc-transport/socket.so
> #9 0x0000003efac7d060 in ?? () from /usr/lib64/libglusterfs.so.0
> #10 0x00000035324079d1 in start_thread () from /lib64/libpthread.so.0
> #11 0x00000035320e89dd in clone () from /lib64/libc.so.6
Seema,
I believe Gaurav has already clarified about it. Clearing the needinfo.
Thanks,
Atin
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list