[LU-15383] DNE directories not connected to REMOTE_PARENT_DIR

• Type: Bug
• Resolution: Unresolved
• Priority: Critical
• Severity: 3
• Assignee: Lai Siyao
• Reporter: Andreas Dilger

Description

Running e2fsck on an MDT with a large number of striped directories shows a large number of disconnected directory entries. On several different systems this is showing a large number of errors during e2fsck, resulting in tens or hundreds of thousands of entries that need to be connected to list+found:

Unconnected directory inode 2102494 (/REMOTE_PARENT_DIR/???)
Connect to /lost+found? yes
Unconnected directory inode 2102510 (/REMOTE_PARENT_DIR/???)
Connect to /lost+found? yes
Unconnected directory inode 2102514 (/REMOTE_PARENT_DIR/???)
Connect to /lost+found? yes

This doesn't appear to be caused by filesystem errors, as it has been seen repeatedly, so it is more likely to be a bug in the code (eg. rename doesn't connect striped directories properly, maybe if the rename source was on a remote MDT and the target is on the local MDT, or the reverse, or during "lfs migrate -m" or similar.

Issue Links

• Clones: LU-15330 ext2fs_get_pathname() very slow for large directory
• 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-10329 DNE3: REMOTE_PARENT_DIR scalability