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

[LU-5512] LFSCK 3: repair dangling name entry Created: 20/Aug/14  Updated: 30/Sep/14  Resolved: 30/Sep/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): 15369

 Description   

If the MDT-object referenced by the name entry is lost, then the namespace LFSCK needs to repair the inconsistency as required:

1) Keep the inconsistency there and report the inconsistency case, then give the chance to the application to find related issues, and the users can make the decision about how to handle it with more human knownledge. (by default)

2) Re-create the missed MDT-object with the FID (in the name entry)

The LFSCK will allow the administrator to specify how to handle the dangling name entry when trigger the LFSCK:



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

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

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

The patch has been landed to master.

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