Project

General

Profile

Actions

Bug #21363

closed

ceph-fuse crashing while mounting cephfs

Added by Prashant D over 6 years ago. Updated over 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Community (dev)
Tags:
v10.2.9
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
fs
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When trying to mount cephfs using ceph-fuse on ubuntu 16.04.3, parent or child ceph-fuse process getting SIGABRT signal. Though, the filesystem seems to mounted and data can be read/written.

The cluster and ceph client running ceph version 10.2.9 (2ee413f77150c0f375ff6f10edd6c8f9c7d060d0)

Here is the gdb bracktrace for the coredump of ceph-fuse :
  1. gdb /usr/bin/ceph-fuse core
    GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
    Copyright (C) 2016 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "x86_64-linux-gnu".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    <http://www.gnu.org/software/gdb/bugs/&gt;.
    Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/&gt;.
    For help, type "help".
    Type "apropos word" to search for commands related to "word"...
    Reading symbols from /usr/bin/ceph-fuse...Reading symbols from /usr/lib/debug//usr/bin/ceph-fuse...done.
    done.
    [New LWP 15940]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    Core was generated by `ceph-fuse -n client.cephfs -m rcceph02-01-ac:6789 -k /etc/ceph/ceph.client.ceph'.
    Program terminated with signal SIGABRT, Aborted.
    #0 0x00007fa68b3a2269 in raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/pt-raise.c:35
    35 ../sysdeps/unix/sysv/linux/pt-raise.c: No such file or directory.
    (gdb) bt
    #0 0x00007fa68b3a2269 in raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/pt-raise.c:35
    #1 0x000055f2f21260bc in reraise_fatal (signum=6) at global/signal_handler.cc:71
    #2 handle_fatal_signal (signum=6) at global/signal_handler.cc:133
    #3 <signal handler called>
    #4 0x00007fa689bb0428 in GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
    #5 0x00007fa689bb202a in _GI_abort () at abort.c:89
    #6 0x00007fa689ba8bd7 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x55f2f23da6af "is_started()", file=file@entry=0x55f2f23da6a3 "log/Log.cc", line=line@entry=434,
    function=function@entry=0x55f2f23da840 <ceph::log::Log::stop()::
    _PRETTY_FUNCTION
    > "void ceph::log::Log::stop()") at assert.c:92
    #7 0x00007fa689ba8c82 in GIassert_fail (assertion=assertion@entry=0x55f2f23da6af "is_started()", file=file@entry=0x55f2f23da6a3 "log/Log.cc", line=line@entry=434,
    function=function@entry=0x55f2f23da840 <ceph::log::Log::stop()::
    _PRETTY_FUNCTION__> "void ceph::log::Log::stop()") at assert.c:101
    #8 0x000055f2f21612c4 in ceph::log::Log::stop (this=0x55f2fc508000) at log/Log.cc:434
    #9 0x000055f2f22437c4 in CephContext::~CephContext (this=0x55f2fc4e0000, __in_chrg=<optimized out>) at common/ceph_context.cc:558
    #10 0x000055f2f22439bc in CephContext::put (this=0x55f2fc4e0000) at common/ceph_context.cc:578
    #11 0x000055f2f200d64c in boost::intrusive_ptr<CephContext>::~intrusive_ptr (this=0x7fff66b613c0, __in_chrg=<optimized out>) at /usr/include/boost/smart_ptr/intrusive_ptr.hpp:97
    #12 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ceph_fuse.cc:83
    (gdb)

It seems process got coredump when log thread was being stopped during CephContext object deletion, the log thread seems to have not started and thread_id being 0 asserted in process getting SIGABRT.


Files

core.15940.tgz (445 KB) core.15940.tgz ceph-fuse Core file Prashant D, 09/12/2017 02:18 AM

Related issues 1 (0 open1 closed)

Is duplicate of CephFS - Backport #20972: jewel ceph-fuse segfaults at mount time, assert in ceph::log::Log::stopResolvedNathan CutlerActions
Actions #1

Updated by Shinobu Kinjo over 6 years ago

3242b2b should fix the issue.

Actions #2

Updated by Prashant D over 6 years ago

The issue#20972 has already been fixed in PR 16963.

[1] http://tracker.ceph.com/issues/20972
[2] https://github.com/ceph/ceph/pull/16963

Actions #3

Updated by Shinobu Kinjo over 6 years ago

  • Status changed from New to Closed
Actions #4

Updated by Patrick Donnelly over 6 years ago

  • Is duplicate of Backport #20972: jewel ceph-fuse segfaults at mount time, assert in ceph::log::Log::stop added
Actions #5

Updated by Patrick Donnelly over 6 years ago

  • Project changed from Ceph to CephFS
  • Category deleted (129)
  • Status changed from Closed to Duplicate
Actions

Also available in: Atom PDF