Actions
Feature #18509
closedMDS: damage reporting by ino number is useless
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
jewel, kraken
Reviewed:
Affected Versions:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Description
We had two damaged directories on the long-running cluster, but examining the directories in question (other than through raw RADOS) is pretty difficult.
[{"damage_type":"dir_frag","id":106068496,"ino":1099586093270,"frag":"*"},{"damage_type":"dir_frag","id":2243167668,"ino":1099586138404,"frag":"*"}]When we generate a damage report a little more info is sent to clog, but we can't find any entries and think it was so long ago the files have been logrotated into nothingness.
In a reasonably healthy cluster one could also look at the raw RADOS objects, but assuming I've done the name translation correctly, we actually have lost these objects!
Actions