All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Assertion in v0.40 - os/FileStore.cc: 2438: FAILED assert(0 == "unexpected error")
Date: Sun, 15 Jan 2012 12:39:37 +0100	[thread overview]
Message-ID: <4F12BAF9.4040301@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1201141835180.21391@cobra.newdream.net>

Hi Sage,
that's exactly what I did, the first two crashes are in this log, 
unfortunately there was no debug level set.

http://85.214.49.87/ceph/osd.0.full.log.bz2

-martin



Am 15.01.2012 03:45, schrieb Sage Weil:
> Hi Martin-
>
> On Sat, 14 Jan 2012, Martin Mailand wrote:
>
>> Hi
>> one of four OSD died during the update to v0.40 with an Assertion
>> os/FileStore.cc: 2438: FAILED assert(0 == "unexpected error")
>> Even after a complete shutdown of the cluster an a new start with all OSD at
>> the same version, this osd did not start.
>>
>> The OSD Log it attached.
>
> It's trying to replay a transaction that appears to be invalid because the
> .2 clone is smaller than it thinks.  Is this the first time the OSD
> crashed, or did it crash once, and you cranked up logs and generated
> this one?  If you have the previous log, that would be helpful... it
> should have a similar tranasction dump but a different stack trace.
>
> Also, are any of the 6 patches on top of 0.40 related to the filestore or
> osd?
>
> Thanks!
> sage
>

  parent reply	other threads:[~2012-01-15 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-14 14:40 Assertion in v0.40 - os/FileStore.cc: 2438: FAILED assert(0 == "unexpected error") Martin Mailand
2012-01-15  2:45 ` Sage Weil
2012-01-15  5:52   ` Sage Weil
2012-01-15 11:41     ` Martin Mailand
2012-01-15 11:39   ` Martin Mailand [this message]
2012-01-16  6:14     ` Sage Weil

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=4F12BAF9.4040301@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /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.