Project

General

Profile

Actions

Feature #12136

open

fsck: snapshots: Enumerate snapshots during scan_extents

Added by John Spray almost 9 years ago. Updated about 5 years ago.

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

0%

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

Description

Optionally, issue a RADOS op to list all the snapshots for every object seen, and accumulate these into a set on the zeroth inode.

If the snapshots match a snaprealm that already exists in the metadata tree for where we will inject the inode, then we can restore these. If not, we would either have to synthesize snaprealms (perhaps not a straightforward thing to do) or at least report their existence to the user and provide an option to go delete the now-orphaned snapshot versions of file data.

It seems likely (to me: subjective) that in the latter case, the system is sufficiently damaged that users will mainly want their latest version of the file back, and probably won't trust any recovered snapshot state enough for it to be useful.

Actions #1

Updated by John Spray over 8 years ago

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

Updated by Greg Farnum almost 8 years ago

  • Subject changed from cephfs-data-scan: Enumerate snapshots during scan_extents to fsck: snapshots: Enumerate snapshots during scan_extents
  • Category changed from fsck/damage handling to 89
Actions #3

Updated by Patrick Donnelly about 5 years ago

  • Labels (FS) snapshots added
Actions #4

Updated by Patrick Donnelly about 5 years ago

  • Category deleted (89)
Actions

Also available in: Atom PDF