From: Stefan Priebe <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD crash
Date: Sat, 16 Jun 2012 15:34:14 +0200 [thread overview]
Message-ID: <4FDC8B56.7080507@profihost.ag> (raw)
In-Reply-To: <4FDC82BA.5030102@profihost.ag>
and another crash again ;-(
0> 2012-06-16 15:31:32.524369 7fd8935c4700 -1 ./common/Mutex.h: In
function 'void Mutex::Lock(bool)' thread 7fd8935c4700 time 2012-06-16
15:31:32.522446
./common/Mutex.h: 110: FAILED assert(r == 0)
ceph version (commit:)
1: /usr/bin/ceph-osd() [0x51a07d]
2: (ReplicatedPG::C_OSD_OndiskWriteUnlock::finish(int)+0x2a) [0x579c5a]
3: (FileStore::_finish_op(FileStore::OpSequencer*)+0x2e4) [0x684374]
4: (ThreadPool::worker()+0xbb7) [0x7bc087]
5: (ThreadPool::WorkThread::entry()+0xd) [0x5f144d]
6: (()+0x68ca) [0x7fd89db3a8ca]
7: (clone()+0x6d) [0x7fd89c1bec0d]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is
needed to interpret this.
--- end dump of recent events ---
2012-06-16 15:31:32.531567 7fd8935c4700 -1 *** Caught signal (Aborted) **
in thread 7fd8935c4700
ceph version (commit:)
1: /usr/bin/ceph-osd() [0x70e4b9]
2: (()+0xeff0) [0x7fd89db42ff0]
3: (gsignal()+0x35) [0x7fd89c121225]
4: (abort()+0x180) [0x7fd89c124030]
5: (__gnu_cxx::__verbose_terminate_handler()+0x115) [0x7fd89c9b5dc5]
6: (()+0xcb166) [0x7fd89c9b4166]
7: (()+0xcb193) [0x7fd89c9b4193]
8: (()+0xcb28e) [0x7fd89c9b428e]
9: (ceph::__ceph_assert_fail(char const*, char const*, int, char
const*)+0x940) [0x78af20]
10: /usr/bin/ceph-osd() [0x51a07d]
11: (ReplicatedPG::C_OSD_OndiskWriteUnlock::finish(int)+0x2a) [0x579c5a]
12: (FileStore::_finish_op(FileStore::OpSequencer*)+0x2e4) [0x684374]
13: (ThreadPool::worker()+0xbb7) [0x7bc087]
14: (ThreadPool::WorkThread::entry()+0xd) [0x5f144d]
15: (()+0x68ca) [0x7fd89db3a8ca]
16: (clone()+0x6d) [0x7fd89c1bec0d]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is
needed to interpret this.
--- begin dump of recent events ---
0> 2012-06-16 15:31:32.531567 7fd8935c4700 -1 *** Caught signal
(Aborted) **
in thread 7fd8935c4700
ceph version (commit:)
1: /usr/bin/ceph-osd() [0x70e4b9]
2: (()+0xeff0) [0x7fd89db42ff0]
3: (gsignal()+0x35) [0x7fd89c121225]
4: (abort()+0x180) [0x7fd89c124030]
5: (__gnu_cxx::__verbose_terminate_handler()+0x115) [0x7fd89c9b5dc5]
6: (()+0xcb166) [0x7fd89c9b4166]
7: (()+0xcb193) [0x7fd89c9b4193]
8: (()+0xcb28e) [0x7fd89c9b428e]
9: (ceph::__ceph_assert_fail(char const*, char const*, int, char
const*)+0x940) [0x78af20]
10: /usr/bin/ceph-osd() [0x51a07d]
11: (ReplicatedPG::C_OSD_OndiskWriteUnlock::finish(int)+0x2a) [0x579c5a]
12: (FileStore::_finish_op(FileStore::OpSequencer*)+0x2e4) [0x684374]
13: (ThreadPool::worker()+0xbb7) [0x7bc087]
14: (ThreadPool::WorkThread::entry()+0xd) [0x5f144d]
15: (()+0x68ca) [0x7fd89db3a8ca]
16: (clone()+0x6d) [0x7fd89c1bec0d]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is
needed to interpret this.
--- end dump of recent events ---
Am 16.06.2012 14:57, schrieb Stefan Priebe:
> Hi,
>
> today i got another osd crash ;-( Strangely the osd logs are all empty.
> It seems the logrotate hasn't reloaded the daemons but i still have the
> core dump file? What's next?
>
> Stefan
>
next prev parent reply other threads:[~2012-06-16 13:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 12:57 OSD crash Stefan Priebe
2012-06-16 13:34 ` Stefan Priebe [this message]
2012-06-17 21:16 ` Sage Weil
2012-06-18 6:41 ` Stefan Priebe - Profihost AG
-- strict thread matches above, loose matches on Subject: below --
2020-09-07 16:42 osd crash Kaarlo Lahtela
[not found] <8566685.312.1362419807745.JavaMail.dspano@it1>
2013-03-04 18:02 ` OSD Crash Dave Spano
2012-08-22 20:31 OSD crash Andrey Korolyov
2012-08-22 22:33 ` Sage Weil
2012-08-22 22:55 ` Andrey Korolyov
2012-08-23 0:09 ` Gregory Farnum
2012-08-25 8:30 ` Andrey Korolyov
2012-08-26 16:52 ` Andrey Korolyov
2012-08-26 20:44 ` Sage Weil
2012-09-04 8:13 ` Andrey Korolyov
2012-09-04 15:32 ` Sage Weil
2011-05-27 0:12 Fyodor Ustinov
2011-05-27 15:16 ` Gregory Farnum
2011-05-27 16:41 ` Fyodor Ustinov
2011-05-27 16:49 ` Gregory Farnum
2011-05-27 19:18 ` Gregory Farnum
2011-05-27 19:30 ` Fyodor Ustinov
2011-05-27 22:52 ` Fyodor Ustinov
2011-05-11 20:47 OSD Crash Mark Nigh
2011-05-11 21:06 ` Sage Weil
2011-05-11 21:39 ` Colin McCabe
2011-05-13 17:03 ` Mark Nigh
2011-05-13 18:34 ` Sage Weil
2011-05-11 13:12 Mark Nigh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FDC8B56.7080507@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox