From: Daniel Poelzleithner <poelzleithner@b1-systems.de>
To: ceph-devel@vger.kernel.org
Subject: Re: [PATCH] Fix for corrupted ceph cluster
Date: Thu, 06 Mar 2014 00:03:52 +0100 [thread overview]
Message-ID: <5317AD58.1060705@b1-systems.de> (raw)
In-Reply-To: <52F9C7A1.3060705@b1-systems.de>
On 02/11/2014 07:48 AM, Daniel Poelzleithner wrote:
> I wrote a small patch that ignores object_trim requests when he does not
> find the context of this request.
> We have a node that fails to start permanently and there is no way to
> get all nodes back up.
[...]
> This is regarding bug http://tracker.ceph.com/issues/6101
The patch now ran for 2 weeks and the 4th node is working again.
I think this patch is safe to apply, but not fixing the underlying problem.
Some state in ceph causes the delete event to be triggered every some
seconds and causes a log entry to be generated.
Do you need more informations to find the cause ? This definitely is
some wired internal state and is no race condition.
kind regards
Daniel
next prev parent reply other threads:[~2014-03-05 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 6:48 [PATCH] Fix for corrupted ceph cluster Daniel Poelzleithner
2014-03-05 23:03 ` Daniel Poelzleithner [this message]
2014-03-05 23:12 ` 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=5317AD58.1060705@b1-systems.de \
--to=poelzleithner@b1-systems.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.