Project

General

Profile

Bug #18113

Don't lose deep-scrub information

Added by David Zafman 12 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
12/02/2016
Due date:
% Done:

0%

Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Needs Doc:
No

Description

We'd like to not lose deep-scrub information when more frequent scrub happens.


Related issues

Duplicated by Ceph - Feature #14860: scrub/repair: persist scrub results (do not overwrite deep scrub results with non-deep scrub) Duplicate 10/16/2015
Copied to Ceph - Backport #18502: jewel: Don't lose deep-scrub information Resolved

History

#2 Updated by David Zafman 12 months ago

The only issue that became obvious when modifying the code is what to do if nodeep-scrub flag is set.

Sam Just:
Hmm, that's a good point. Probably, it would be best to refuse to do a shallow scrub and output a WRN message to clog.

#3 Updated by David Zafman 10 months ago

  • Status changed from New to Resolved

#4 Updated by David Zafman 10 months ago

  • Status changed from Resolved to Pending Backport
  • Backport changed from Jewel to Jewel, Kraken

#5 Updated by Loic Dachary 10 months ago

  • Backport changed from Jewel, Kraken to jewel,kraken

#6 Updated by Loic Dachary 10 months ago

  • Copied to Backport #18502: jewel: Don't lose deep-scrub information added

#8 Updated by Nathan Cutler 10 months ago

  • Backport changed from jewel,kraken to jewel

The commits were manually merged to kraken before the 11.2.0 release, so kraken backport is not needed.

#10 Updated by David Zafman 9 months ago

  • Duplicated by Feature #14860: scrub/repair: persist scrub results (do not overwrite deep scrub results with non-deep scrub) added

#11 Updated by David Zafman 4 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF