[LU-14570] e2fsck reports "Entry '..' an incorrect filetype (was 18, should be 1)"

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Labels: e2fsck
• Severity: 3
• Assignee: Core Lustre Triage
• Reporter: Andreas Dilger

Description

Running e2fsck on a DNE filesystem where LFSCK was run reported:

Entry '..' in <195395086>/<195395122> (195395122) has an incorrect filetype (was 18, should be 1).
Entry '..' in <602879868>/<602879869> (602879869) has an incorrect filetype (was 18, should be 1).
Entry '..' in <134818057>/<134818059> (134818059) has an incorrect filetype (was 18, should be 1).
Entry '..' in <134818057>/<134818064> (134818064) has an incorrect filetype (was 18, should be 1).
Entry '..' in <134818057>/<134818066> (134818066) has an incorrect filetype (was 18, should be 1).

This is because the entry file_type has a flag EXT2_DIRENT_LUFID when the dirdata feature stores the FID in the directory entry, and it should be masked when checking the file type.

Issue Links

• is related to: LU-15913 rename stress test leads to REMOTE_PARENT_DIR corruption