Project

General

Profile

Actions
Copy link

Bug #13493

closed

osd: for ec, cascading crash during recovery if one shard is corrupted

Added by Guang Yang over 8 years ago. Updated almost 7 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
David Zafman
Category:
EC Pools
Target version:
-
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

For EC pool, during recovery, if there is one shard corrupted, it would cascade crash the OSDs until the PG is down (as once the primary is crashed, the secondary would become primary and start recovering, and then crash when recovering the object).

Related issues 1 (0 open — 1 closed)

Is duplicate of Ceph - Bug #13937: osd/ECBackend.cc: 201: FAILED assert(res.errors.empty())ResolvedDavid Zafman12/01/2015

Actions
Actions
Copy link
 #1

Updated by Guang Yang over 8 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by Yehuda Sadeh over 8 years ago

  • Project changed from rgw to Ceph
Actions
Copy link
 #3

Updated by Greg Farnum almost 7 years ago

  • Project changed from Ceph to RADOS
  • Category set to EC Pools
  • Assignee changed from Guang Yang to David Zafman
  • Component(RADOS) OSD added

I suspect this is being resolved by David's work on EIO handling?

Actions
Copy link
 #4

Updated by David Zafman almost 7 years ago

  • Is duplicate of Bug #13937: osd/ECBackend.cc: 201: FAILED assert(res.errors.empty()) added
Actions
Copy link
 #5

Updated by David Zafman almost 7 years ago

  • Status changed from In Progress to Duplicate
Actions
Copy link

Also available in: Atom PDF