LFSCK 3: MDT-MDT consistency verification (LU-4788)

[LU-5517] LFSCK 3: repair invalid nlink count Created: 20/Aug/14  Updated: 30/Oct/14  Resolved: 30/Oct/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.7.0
Fix Version/s: Lustre 2.7.0

Type: Technical task Priority: Major
Reporter: nasf (Inactive) Assignee: nasf (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Rank (Obsolete): 15374

 Description   

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.



 Comments   
Comment by nasf (Inactive) [ 20/Aug/14 ]

Here is the patch:
http://review.whamcloud.com/#/c/11516/

Comment by nasf (Inactive) [ 30/Oct/14 ]

The patch has been landed to master.

Generated at Sat Feb 10 01:52:09 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.