Project

General

Profile

Actions
Copy link

Feature #12141

open

cephfs-data-scan: File size correction from backward scan

Added by John Spray almost 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:

Description

Currently, if a dentry already exists at the backtrace location which points to the inode, we do nothing. We should optionally correct the size of the file, if what we scan differs from the content of the dentry.

This would be useful for cases where e.g. we killed a journal such that the MDSs don't know a file was recently written to, or where a client misbehaved.

Actions
Copy link
 #1

Updated by John Spray over 8 years ago

  • Category changed from 66 to fsck/damage handling
Actions
Copy link
 #2

Updated by Greg Farnum almost 8 years ago

  • Assignee set to Douglas Fuller
Actions
Copy link
 #3

Updated by Greg Farnum almost 8 years ago

This was discussed elsewhere, but we need to be able to disable file size correction as well – via a config option at first, but eventually on an inode basis or similar.

Actions
Copy link
 #4

Updated by Greg Farnum over 7 years ago

  • Assignee deleted (Douglas Fuller)

Unassigning as I believe this was dropped?

Actions
Copy link

Also available in: Atom PDF