Actions
Feature #12281
openRespect PIN_SCRUBQUEUE from StrayManager
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
When purging, the StrayManager needs to notice metadata subject to PIN_SCRUBQUEUE and unhook items from the scrub subsystem where necessary before purging. It also needs to respect the Locker locks that forward scrub uses while actually performing RADOS ops on a scrubbed dentry: the assumption that a stray dentry with nlink=0 has no locks may cease to be true, or we may need to make it true by removing inodes from scrubqueue when their nlink reaches 0.
No data to display
Actions