[LU-14168] e2fsck should avoid moving files into lost+found

• Type: Improvement
• Resolution: Unresolved
• Priority: Major
• Labels: e2fsprogs
• Assignee: WC Triage
• Reporter: Andreas Dilger

Description

When e2fsck finds a directory that is hard-linked between an existing directory and lost+found, it appears to prefer moving the file into lost+found rather than keeping it connected to the original parent directory:

'..' in /lost+found/#471345273 (471345273) is /ROOT/RUNDIRS/2018051500/output (471373040), should be /lost+found (11).
Fix? no
Entry 'tmp249767' in /ROOT/RUNDIRS/2018051500/output (471373040) is a link to directory /lost+found/#471345273 (471345273 fid=[0x200039c0f:0x1d51c:0x0]).
Inode 471345273 ref count is 2, should be 3.  Fix? no
Entry '#471345273' in /lost+found (11) has an incorrect filetype (was 1, should be 2).
Fix? no

It would make more sense for e2fsck to prefer not moving files into lost+found if there is somewhere else that the inode could be attached.

Issue Links

• is related to: LU-4876 LFSCK remove entry from /REMOTE_PARENT_DIR if MDT-object name reside on the same MDT after migration
• is related to: LU-15388 Wrong dotdot FID parameter for osd_add_dot_dotdot()
• is related to: LU-14894 Parallel pass2 support for e2fsck