Project

General

Profile

Bug #17518

monitor assertion failure when deactivating mds in (invalid) fscid 0

Added by Patrick Donnelly about 1 year ago. Updated 9 months ago.

Status:
Resolved
Priority:
Urgent
Category:
-
Target version:
-
Start date:
10/05/2016
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Component(FS):
MDSMonitor
Needs Doc:
No

Description

Made a simple vstart cluster and tried this:

$ bin/ceph mds deactivate 0:0
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2016-10-05 14:29:04.026999 7f9bb3802700 -1 WARNING: the following dangerous and experimental features are enabled: *
2016-10-05 14:29:04.038277 7f9bb3802700 -1 WARNING: the following dangerous and experimental features are enabled: *
2016-10-05 14:29:18.902817 7f9ba2ffd700  0 monclient: hunting for new mon
2016-10-05 14:29:39.006848 7f9ba2ffd700  0 monclient: hunting for new mon
[...]

monitor log:

   -2> 2016-10-05 14:29:04.191461 7f93ce080700  4 mon.a@0(leader).mds e6 filesystem_command prefix='mds deactivate'
    -1> 2016-10-05 14:29:04.191467 7f93ce080700  5 -- op tracker -- seq: 65130, time: 2016-10-05 14:29:04.191467, event: mdsmap:filesystem_command, op: mon_command({"prefix": "mds deactivate", "who": "0:0"} v 0)
     0> 2016-10-05 14:29:04.196455 7f93ce080700 -1 *** Caught signal (Aborted) **
 in thread 7f93ce080700 thread_name:ms_dispatch

 ceph version v11.0.0-3134-ga35b7f6 (a35b7f6a67a80862f4829084076ef1d8a095db09)
 1: (()+0x6a92ba) [0x7f93d9f722ba]
 2: (()+0x3c5260f6d0) [0x7f93d5d416d0]
 3: (gsignal()+0x37) [0x7f93d5184877]
 4: (abort()+0x148) [0x7f93d5185f68]
 5: (__gnu_cxx::__verbose_terminate_handler()+0x165) [0x7f93d5a8add5]
 6: (()+0x3c55e5ed46) [0x7f93d5a88d46]
 7: (()+0x3c55e5ed73) [0x7f93d5a88d73]
 8: (()+0x3c55e5ef93) [0x7f93d5a88f93]
 9: (std::__throw_out_of_range(char const*)+0x77) [0x7f93d5adddf7]
 10: (FSMap::parse_role(std::string const&, mds_role_t*, std::ostream&) const+0x45c) [0x7f93d9eeba4c]
 11: (MDSMonitor::filesystem_command(std::shared_ptr<MonOpRequest>, std::string const&, std::map<std::string, boost::variant<std::string, bool, long, double, std::vector<std::string, std::allocator<std::string> >, std::vector<long, std::allocator<long> >, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_>, std::less<std::string>, std::allocator<std::pair<std::string const, boost::variant<std::string, bool, long, double, std::vector<std::string, std::allocator<std::string> >, std::vector<long, std::allocator<long> >, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> > > >&, std::basic_stringstream<char, std::char_traits<char>, std::allocator<char> >&)+0x204) [0x7f93d9c697e4]
 12: (MDSMonitor::prepare_command(std::shared_ptr<MonOpRequest>)+0xa6a) [0x7f93d9c6bc7a]
 13: (MDSMonitor::prepare_update(std::shared_ptr<MonOpRequest>)+0x324) [0x7f93d9c6f864]
 14: (PaxosService::dispatch(std::shared_ptr<MonOpRequest>)+0xf72) [0x7f93d9beafc2]
 15: (Monitor::handle_command(std::shared_ptr<MonOpRequest>)+0x1c06) [0x7f93d9ba4116]
 16: (Monitor::dispatch_op(std::shared_ptr<MonOpRequest>)+0x314) [0x7f93d9bb17d4]
 17: (Monitor::_ms_dispatch(Message*)+0x6b9) [0x7f93d9bb2b29]
 18: (Monitor::handle_forward(std::shared_ptr<MonOpRequest>)+0xb09) [0x7f93d9bb0ed9]
 19: (Monitor::dispatch_op(std::shared_ptr<MonOpRequest>)+0xc0a) [0x7f93d9bb20ca]
 20: (Monitor::_ms_dispatch(Message*)+0x6b9) [0x7f93d9bb2b29]
 21: (Monitor::ms_dispatch(Message*)+0x23) [0x7f93d9bd2cd3]
 22: (DispatchQueue::entry()+0x7ba) [0x7f93d9f2c69a]
 23: (DispatchQueue::DispatchThread::entry()+0xd) [0x7f93d9e0925d]
 24: (()+0x3c52607ee5) [0x7f93d5d39ee5]
 25: (clone()+0x6d) [0x7f93d5243d1d]
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.

Related issues

Copied to fs - Backport #17582: jewel: monitor assertion failure when deactivating mds in (invalid) fscid 0 Resolved

History

#1 Updated by Patrick Donnelly about 1 year ago

  • Subject changed from monitor segfault when deactivating mds in (invalid) fscid 0 to monitor assertion failure when deactivating mds in (invalid) fscid 0

#2 Updated by Patrick Donnelly about 1 year ago

  • Status changed from New to Need Review

#3 Updated by John Spray about 1 year ago

  • Status changed from Need Review to Pending Backport
  • Backport set to jewel

#4 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #17582: jewel: monitor assertion failure when deactivating mds in (invalid) fscid 0 added

#5 Updated by Patrick Donnelly 9 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF