From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Upgrading from 0.61.5 to 0.61.6 ended in disaster
Date: Wed, 24 Jul 2013 12:11:12 +0100 [thread overview]
Message-ID: <51EFB650.6050506@inktank.com> (raw)
In-Reply-To: <51EF843D.1070107@profihost.ag>
On 07/24/2013 08:37 AM, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> i uploaded my ceph mon store to cephdrop
> /home/cephdrop/ceph-mon-failed-assert-0.61.6/mon.tar.gz.
>
> So hopefully someone can find the culprit soon.
>
> It fails in OSDMonitor.cc here:
>
> // if we trigger this, then there's something else going with the store
> // state, and we shouldn't want to work around it without knowing what
> // exactly happened.
> assert(latest_full > 0);
>
Wrong variable being used in a loop as part of a workaround for 5704.
Opened a bug for this on http://tracker.ceph.com/issues/5737
A fix is available on wip-5737 (next) and wip-5737-cuttlefish.
Tested the mon against your store and it worked flawlessly. Also tested
it against the same stores used during the original fix and also they
worked just fine.
My question now is how the hell those stores worked fine although the
original fix was grabbing what should have been a non-existent version,
or how did they not trigger that assert. Which is what I'm going to
investigate next.
-Joao
--
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com
next prev parent reply other threads:[~2013-07-24 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 7:05 Upgrading from 0.61.5 to 0.61.6 ended in disaster Stefan Priebe - Profihost AG
2013-07-24 7:37 ` Stefan Priebe - Profihost AG
2013-07-24 10:42 ` Joao Eduardo Luis
2013-07-24 11:11 ` Joao Eduardo Luis [this message]
2013-07-24 11:54 ` Stefan Priebe - Profihost AG
2013-07-24 15:29 ` Sage Weil
2013-07-24 23:19 ` Sage Weil
2013-07-25 6:19 ` Stefan Priebe - Profihost AG
-- strict thread matches above, loose matches on Subject: below --
2013-07-25 11:19 peter
2013-07-25 15:46 ` Sage Weil
2013-07-25 16:12 ` peter
2013-07-29 9:40 ` peter
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=51EFB650.6050506@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.