[LU-5517] LFSCK 3: repair invalid nlink count

Thu, 30 Oct 2014 02:16:22 +0000

If the namespace LFSCK has verified all the known name entries during the first-stage scanning, then the object's linkEA is trustable. So if the non-directory object's nlink attribute does not match its linkEA entries count, then the LFSCK will repair the nlink attribute according to the linkEA entries count.

One exception is that: the linkEA space is limited, if there are too much hard links on the object and exceeds the object's linkEA space limitation, then some name entries cannot be recorded in the linkEA. Under such case, we will add some flags in the LFSCK tracing file for related objects. Then the LFSCK can skip the nlink attribute verification for those objects during the second-stage scanning.

Whamcloud Community JIRA

[LU-5517] LFSCK 3: repair invalid nlink count