Project

General

Profile

Feature #19657

An EIO from a single device should not be a client-visible failure.

Added by David Zafman almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Sage:
the underlying goal: any EIO from a single device should not be a client-visible failure.
(the same way an OSD failure shouldn't be visible to client workloads)

we get this by enabling the eio on read config option, but the goal would be to do better than that: trigger a repair on an object that gives EIO on read, just like we do during scrub.
(well, during repair)

or, if we don't repair, work around it by reading from a replica that doesn't return eio.
(which might make more sense since repair after scrub pbly won't be driven directly by the osd in the future?)

davidz
ok. yes… eventually repair is moving out of osd and we won't be using recovery to do it (hopefully). We could use that mechanism for now I guess.
Or as you say may we just read from another replica


Related issues

Duplicated by RADOS - Bug #20863: CRC error does not mark PG as inconsistent or queue for repair Duplicate 07/31/2017

History

#1 Updated by David Zafman almost 4 years ago

  • Priority changed from Normal to Urgent

#2 Updated by David Zafman almost 4 years ago

  • Target version set to v12.1.0

#3 Updated by David Zafman over 3 years ago

  • Status changed from New to In Progress

#5 Updated by David Zafman over 3 years ago

  • Status changed from In Progress to Resolved

#6 Updated by David Zafman over 3 years ago

  • Duplicated by Bug #20863: CRC error does not mark PG as inconsistent or queue for repair added

Also available in: Atom PDF