From: David Zafman <dzafman@redhat.com>
To: Markus Blank-Burian <burian@muenster.de>
Cc: 'Ceph Development' <ceph-devel@vger.kernel.org>
Subject: Re: Error handling during recovery read
Date: Fri, 4 Dec 2015 18:24:46 -0800 [thread overview]
Message-ID: <56624AEE.7020605@redhat.com> (raw)
In-Reply-To: <DUB403-EAS1052ED1A42AB6DFDA68D8BD50C0@phx.gbl>
I can't remember the details now, but I know that recovery needed
additional work. If it were a simple fix
I would have done it when implementing that code.
I found this bug related to recovery and ec errors
(http://tracker.ceph.com/issues/13493)
BUG #13493: osd: for ec, cascading crash during recovery if one shard is
corrupted
David
On 12/4/15 2:03 AM, Markus Blank-Burian wrote:
> Hi David,
>
>
>
> I am using ceph 9.2.0 with an erasure coded pool and have some problems with
> missing objects.
>
>
>
> Reads for degraded/backfilling objects on an EC pool, which detect an error
> (-2 in my case) seem to be aborted immediately instead of reading from the
> remaining shards. Why is there an explicit check for "!rop.for_recovery" in
> ECBackend::handle_sub_read_reply? Would it be possible to remove this check
> and let the recovery read be completed from the remaining good shards?
>
>
>
> Markus
>
>
>
>
parent reply other threads:[~2015-12-05 2:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DUB403-EAS1052ED1A42AB6DFDA68D8BD50C0@phx.gbl>]
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=56624AEE.7020605@redhat.com \
--to=dzafman@redhat.com \
--cc=burian@muenster.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.