Project

General

Profile

Actions
Copy link

Bug #41191

closed

osd: scrub error on big objects; make bluestore refuse to start on big objects

Added by Neha Ojha over 4 years ago. Updated over 4 years ago.

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

0%

Source:
Tags:
Backport:
luminous,mimic,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
29579
Crash signature (v1):
Crash signature (v2):

Related issues 3 (0 open — 3 closed)

Copied to RADOS - Backport #41918: mimic: osd: scrub error on big objects; make bluestore refuse to start on big objectsResolvedNathan CutlerActions
Copied to RADOS - Backport #41919: luminous: osd: scrub error on big objects; make bluestore refuse to start on big objectsResolvedNathan CutlerActions
Copied to RADOS - Backport #41920: nautilus: osd: scrub error on big objects; make bluestore refuse to start on big objectsResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by Neha Ojha over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #2

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41918: mimic: osd: scrub error on big objects; make bluestore refuse to start on big objects added
Actions
Copy link
 #3

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41919: luminous: osd: scrub error on big objects; make bluestore refuse to start on big objects added
Actions
Copy link
 #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41920: nautilus: osd: scrub error on big objects; make bluestore refuse to start on big objects added
Actions
Copy link
 #5

Updated by Florian Haas over 4 years ago

As far as I can see, without this patch there is no way to detect excessively large objects other than doing rados stat on every object in all pools, which is frequently rather impractical. Hence my question: is there an estimate as to when the backports might land, at least the one for Nautilus?

Actions
Copy link
 #6

Updated by Nathan Cutler over 4 years ago

@Florian Marsylle - backports on the way. I'll try to keep my eye on them.

Actions
Copy link
 #7

Updated by Florian Haas over 4 years ago

Thanks! It looks like the backport for Mimic has already landed while the one for Nautilus is still pending. That strikes me as unusual; was this intentional or an omission?

Actions
Copy link
 #8

Updated by Nathan Cutler over 4 years ago

@Florian Marsylle - the explanation is simple: we're working on mimic now. We currently don't have any policy saying "fix X must not go into release Y before release Z".

Actions
Copy link
 #9

Updated by Nathan Cutler over 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF