From: Amon Ott <a.ott@m-privacy.de>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Bug #1047 reproduced
Date: Wed, 21 Dec 2011 13:37:43 +0100 [thread overview]
Message-ID: <201112211337.44363.a.ott@m-privacy.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1112020855440.10925@cobra.newdream.net>
On Friday 02 December 2011 wrote Sage Weil:
> On Fri, 2 Dec 2011, Amon Ott wrote:
> > On Thursday 01 December 2011 you wrote:
> > > On all four nodes of my test cluster, MDS crashes with a trace like
> > > that in bug #1047. Example and ceph.conf attached. Ceph server side is
> > > from git master, last commit ce6572273943ffdca4b7dc5344152d6c35106a2d.
> > >
> > > MDS does not start on any node here, it reliably crashes with that
> > > assert.
> >
> > Does it makes sense for you to keep the cluster in that broken state, so
> > that we can reproduce that bug or test a potential fix? Otherwise, I
> > would recreate the Ceph filesystem to make more tests. I also have a full
> > log of one mds from start to crash here.
>
> Can you attach the log to #1047 for posterity? I'll take a quick look and
> see if there is any further info to gain from the log. I'm guessing the
> actual bug occured before the crash, when the anchor table wasn't updated
> properly, but there may be clues here.
Did you find some time to look into this? The bug makes Ceph unusable for us
even with moderate load. All mds instances die with the same assert, the only
way to recover in that state is to recreate the complete ceph fs and restore
backups.
Amon Ott
--
Dr. Amon Ott
m-privacy GmbH Tel: +49 30 24342334
Am Köllnischen Park 1 Fax: +49 30 24342336
10179 Berlin http://www.m-privacy.de
Amtsgericht Charlottenburg, HRB 84946
Geschäftsführer:
Dipl.-Kfm. Holger Maczkowsky,
Roman Maczkowsky
GnuPG-Key-ID: 0x2DD3A649
--
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:[~2011-12-21 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 8:37 Bug #1047 reproduced Amon Ott
2011-12-02 11:17 ` Amon Ott
2011-12-02 16:57 ` Sage Weil
2011-12-05 10:21 ` Amon Ott
2011-12-06 13:20 ` Amon Ott
2011-12-21 12:37 ` Amon Ott [this message]
2011-12-21 16:18 ` Gregory Farnum
2011-12-21 16:36 ` Amon Ott
2011-12-23 0:27 ` Gregory Farnum
2011-12-23 9:58 ` Amon Ott
2011-12-29 11:30 ` Amon Ott
2012-01-27 14:23 ` Amon Ott
2012-01-27 14:50 ` Sage Weil
2012-01-27 18:54 ` Gregory Farnum
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=201112211337.44363.a.ott@m-privacy.de \
--to=a.ott@m-privacy.de \
--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.