Project

General

Profile

Feature #16016

Populate DamageTable from forward scrub

Added by John Spray over 1 year ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
Start date:
05/25/2016
Due date:
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Reviewed:
User Impact:
Affected Versions:
Release:
Component(FS):
Needs Doc:
No

Description

We detect metadata damage two ways: when we try to read things off disk during normal operation, and when we try to verify what's on disk during forward scrub.

Currently DamageTable is only populated in the first path. The issues detected by forward scrub go to the cluster log, but are not visible to the user when they subsequently go to dump the damage table.

Update the forward scrub code to populate DamageTable when it finds errors.


Related issues

Copied to fs - Backport #20294: jewel: Populate DamageTable from forward scrub Resolved

History

#1 Updated by John Spray about 1 year ago

  • Status changed from New to Need Review

#2 Updated by John Spray about 1 year ago

  • Backport set to jewel
  • Needs Doc set to No

#3 Updated by John Spray about 1 year ago

  • Status changed from Need Review to Resolved

#4 Updated by Nathan Cutler 4 months ago

  • Status changed from Resolved to Pending Backport

#5 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #20294: jewel: Populate DamageTable from forward scrub added

#6 Updated by Nathan Cutler 2 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF