Actions
Bug #1193
closedcmds crashes with stacktrace when using --reset-journal and an invalid rank
% Done:
0%
Source:
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Here are the two stack traces I noticed that are different.
$ /usr/bin/cmds -i dev2 -c /etc/ceph/ceph.conf --reset-journal 11 ** WARNING: Ceph is still under development. Any feedback can be directed ** ** at ceph-devel@vger.kernel.org or http://ceph.newdream.net/. ** osdc/Journaler.cc: In function 'void Journaler::set_layout(ceph_file_layout*)', in thread '0x7f0a09e2c700' osdc/Journaler.cc: 57: FAILED assert(layout.fl_pg_pool == pg_pool) ceph version 0.29 (commit:8e69c39f69936e2912a887247c6e268d1c9059ed) 1: /usr/bin/cmds() [0x6b95f6] 2: (Journaler::_finish_read_head(int, ceph::buffer::list&)+0x42a) [0x6bcc4a] 3: (Objecter::handle_osd_op_reply(MOSDOpReply*)+0x71a) [0x69c15a] 4: (Resetter::ms_dispatch(Message*)+0x41) [0x4b43d1] 5: (SimpleMessenger::dispatch_entry()+0x685) [0x706645] 6: (SimpleMessenger::DispatchThread::entry()+0x1c) [0x4a4a7c] 7: (()+0x6d8c) [0x7f0a0b060d8c] 8: (clone()+0x6d) [0x7f0a09f1304d] ceph version 0.29 (commit:8e69c39f69936e2912a887247c6e268d1c9059ed) 1: /usr/bin/cmds() [0x6b95f6] 2: (Journaler::_finish_read_head(int, ceph::buffer::list&)+0x42a) [0x6bcc4a] 3: (Objecter::handle_osd_op_reply(MOSDOpReply*)+0x71a) [0x69c15a] 4: (Resetter::ms_dispatch(Message*)+0x41) [0x4b43d1] 5: (SimpleMessenger::dispatch_entry()+0x685) [0x706645] 6: (SimpleMessenger::DispatchThread::entry()+0x1c) [0x4a4a7c] 7: (()+0x6d8c) [0x7f0a0b060d8c] 8: (clone()+0x6d) [0x7f0a09f1304d] terminate called after throwing an instance of 'ceph::FailedAssertion' *** Caught signal (Aborted) ** in thread 0x7f0a09e2c700 ceph version 0.29 (commit:8e69c39f69936e2912a887247c6e268d1c9059ed) 1: /usr/bin/cmds() [0x728299] 2: (()+0xfc60) [0x7f0a0b069c60] 3: (gsignal()+0x35) [0x7f0a09e60d05] 4: (abort()+0x186) [0x7f0a09e64ab6] 5: (__gnu_cxx::__verbose_terminate_handler()+0x11d) [0x7f0a0a7176dd] 6: (()+0xb9926) [0x7f0a0a715926] 7: (()+0xb9953) [0x7f0a0a715953] 8: (()+0xb9a5e) [0x7f0a0a715a5e] 9: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x362) [0x6f1a42] 10: /usr/bin/cmds() [0x6b95f6] 11: (Journaler::_finish_read_head(int, ceph::buffer::list&)+0x42a) [0x6bcc4a] 12: (Objecter::handle_osd_op_reply(MOSDOpReply*)+0x71a) [0x69c15a] 13: (Resetter::ms_dispatch(Message*)+0x41) [0x4b43d1] 14: (SimpleMessenger::dispatch_entry()+0x685) [0x706645] 15: (SimpleMessenger::DispatchThread::entry()+0x1c) [0x4a4a7c] 16: (()+0x6d8c) [0x7f0a0b060d8c] 17: (clone()+0x6d) [0x7f0a09f1304d] Aborted
root@dev8:~# /usr/bin/cmds -i dev8 -c /etc/ceph/ceph.conf --reset-journal 12 ** WARNING: Ceph is still under development. Any feedback can be directed ** ** at ceph-devel@vger.kernel.org or http://ceph.newdream.net/. ** old journal was 0~0 new journal start will be 0 (0 bytes past old end) writing journal head *** Caught signal (Floating point exception) ** in thread 0x7f78bcb70700 writing EResetJournal entry Floating point exception
Updated by Greg Farnum almost 13 years ago
- Status changed from New to Resolved
Should be fixed by a pair of commits ending in commit:d1fcffad6c038c6712f1d83735e629017829a2fb
Updated by John Spray over 7 years ago
- Project changed from Ceph to CephFS
- Category deleted (
1) - Target version deleted (
v0.31)
Bulk updating project=ceph category=mds bugs so that I can remove the MDS category from the Ceph project to avoid confusion.
Actions