From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD crashed today in os/JournalingObjectStore.cc
Date: Thu, 06 Dec 2012 10:38:03 +0100 [thread overview]
Message-ID: <50C0677B.4090400@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1212051534530.14332@cobra.newdream.net>
Hi,
here a new dump / crash:
https://www.dropbox.com/s/1qhg0dd0fv17q10/ceph-osd.54.log.gz
Stefan
Am 06.12.2012 00:36, schrieb Sage Weil:
> On Wed, 5 Dec 2012, Stefan Priebe - Profihost AG wrote:
>> There was a dump in the attached log.
>
> The stack trace is there, but with 'debug journal = 0/20' in your conf it
> will also dump all of the journal logging activity leading up to that
> point. Can you reproduce with that enabled? That should tell me why op <
> commited_seq.
>
> Thanks!
> sage
>
>
>>
>> Stefan
>>
>> Am 05.12.2012 um 15:41 schrieb Sage Weil <sage@inktank.com>:
>>
>>> On Wed, 5 Dec 2012, Stefan Priebe - Profihost AG wrote:
>>>> Hello list,
>>>>
>>>> i updated to latest next from today and then after 20 minutes an OSD was
>>>> crashing in os/JournalingObjectStore.cc.
>>>>
>>>> Attached is the log.
>>>
>>> Hmm, this is perplexing. It might just be a bad assert, but I can't see
>>> how it could happen. Any chance you can reproduce with
>>>
>>> debug journal = 0/10
>>>
>>> in the [osd] section? That will give us a dump if it fails the assert.
>>>
>>> Thanks!
>>> s
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-12-06 9:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 9:56 OSD crashed today in os/JournalingObjectStore.cc Stefan Priebe - Profihost AG
2012-12-05 14:41 ` Sage Weil
2012-12-05 16:05 ` Stefan Priebe - Profihost AG
2012-12-05 22:25 ` Stefan Priebe
2012-12-05 22:29 ` Stefan Priebe
2012-12-05 23:36 ` Sage Weil
2012-12-06 9:38 ` Stefan Priebe - Profihost AG [this message]
2012-12-06 14:43 ` Sage Weil
2012-12-06 14:47 ` Stefan Priebe - Profihost AG
2012-12-07 0:38 ` Sage Weil
2012-12-07 7:49 ` Stefan Priebe - Profihost AG
2012-12-07 11:02 ` Sage Weil
2012-12-07 11:29 ` Stefan Priebe - Profihost AG
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=50C0677B.4090400@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.