LFSCK Phase 1.5 - FID-in-Dirent LinkEA Consistency Scope Statement

From Lustre Wiki
Jump to navigation Jump to search

Problem Statement

Over the lifetime of an active filesystem, FID-in-Dirent and linkEA entries may become inconsistent or invalid as the result of:

  • non-graceful shutdown.
  • restoration from MDT file-level backup.
  • upgrade from Lustre-1.8.

An MDT upgraded from Lustre-1.8 has neither FID-in-Dirent nor linkEA is available. Without FID-in-Dirent records, Lustre-2.x will not achieve maximum performance of readdir on the MDT, as it will need to look up the FID for each directory entry from the inode, causing a large increase in IOPS for directory access.

LFSCK 1.5 will implement functionality to verify and rebuild FID-in-Dirent and linkEA. This will be achieved by additional functionality executed while the MDT is iterating over the inodes to verify the FID-in-Dirent name entry is consistent with the FID in the inode LMA. If an inconsistency is discovered it will be repaired or rebuild if FID-in-Dirent name entry is absent. The name entry is also verified that it correctly references the inode linkEA and the inode linkEA points back to the valid name entry. The unmatched or redundant inode linkEA will be removed, and the correct or missed inode linkEA will be added.

In addition, the FID-in-Dirent process will add IGIF FIDs to the dirent for upgraded 1.8 file systems. This additional step will avoid the need to look up the inode when doing readdir.

Project Goals

  • FID-in-DIR and linkEA is available on the MDT restored from file-level backup.
  • FID-in-DIR and linkEA is available on the MDT upgraded from Lustre-1.8 format device.
  • Characterize the performance of LFSCK without filesystem load.
  • Characterize the performance of LFSCK with filesystem load.
  • Land code to Lustre Community Release master branch.


  • Kernel-space FID-in-Dirent and linkEA checking and repairing on single MDT.
  • User-space tools to control LFSCK for for FID-in-Dirent and linkEA consistency.
  • Administrative documentation in the form of a man page and update to Intel Lustre-2.x manual.

Out of Scope

  • The LFSCK for FID-in-Dirent and linkEA will be implemented against the inode iterator introduced in LFSCK phase I. Only ldiskfs OSDs will be implemented, tested and landed for this phase.
  • LFSCK for FID-in-Dirent and linkEA consistency will act only on a single MDT at this phase.
  • Detection and resolution of internal file-system inconsistencies is not within LFSCK scope.


  • FID-in-Dirent In Lustre-2.x, when a file is created its FID will be stored as part of the name entry in its parent directory. This is known as FID-in-Directory-Entry or 'FID-in-Dirent.' With the FID-in-Dirent, the readdir on MDT can find the file FID in the directory page directly. Without FID-in-Dirent, the directory page must be identified by reading from inode LMA. As a result, traversing the directory (such as "ls") is accelerated with FID-in-Dirent.
  • linkEA In Lustre-2.x, when a file is created or hard linked, the name together with the parent directory FID are stored as extended attributes. This is known as link-extended-attributes, or linkEA. With the linkEA the given FID can be parsed back to a full path from the root to the target file. This is useful for Changelog based applications, such as lustre_rsync.