From: Burkhard Linke <Burkhard.Linke@computational.bio.uni-giessen.de>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Monitor crash after changing replicated crush rulesets in jewel
Date: Tue, 23 Aug 2016 09:11:51 +0200 [thread overview]
Message-ID: <495353bf-92ea-28ea-9dea-fe12ca6a26e2@computational.bio.uni-giessen.de> (raw)
In-Reply-To: <CAJ4mKGZ6DtdQYtBhHqW35Kkz7OPJHZznwvb5_os9yQ0OxxaTMQ@mail.gmail.com>
Hi,
On 08/22/2016 10:12 PM, Gregory Farnum wrote:
> I didn't dig into it, but maybe compare to
> http://tracker.ceph.com/issues/16525 and see if they're the same
> issue? Or search for other monitor crashes with CRUSH.
Thanks for having a look at it.
It seems to be related to http://tracker.ceph.com/issues/16653 ,
since there's no 'ruleset: 1' in our setup. I'll cleanup our rule sets
and try to remove all
'holes' in the associations.
Regards,
Burkhard
prev parent reply other threads:[~2016-08-23 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 11:58 Monitor crash after changing replicated crush rulesets in jewel Burkhard Linke
2016-08-22 20:12 ` Gregory Farnum
2016-08-23 7:11 ` Burkhard Linke [this message]
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=495353bf-92ea-28ea-9dea-fe12ca6a26e2@computational.bio.uni-giessen.de \
--to=burkhard.linke@computational.bio.uni-giessen.de \
--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 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.