* Re: Error handling during recovery read
[not found] <DUB403-EAS1052ED1A42AB6DFDA68D8BD50C0@phx.gbl>
@ 2015-12-05 2:24 ` David Zafman
0 siblings, 0 replies; only message in thread
From: David Zafman @ 2015-12-05 2:24 UTC (permalink / raw)
To: Markus Blank-Burian; +Cc: 'Ceph Development'
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
>
>
>
>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-12-05 2:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <DUB403-EAS1052ED1A42AB6DFDA68D8BD50C0@phx.gbl>
2015-12-05 2:24 ` Error handling during recovery read David Zafman
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.