[LU-6350] LFSCK 4: lock the MDT-object based on prediction for preparing bad linkEA

• Type: Technical task
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.8.0
• Assignee: nasf (Inactive)
• Reporter: nasf (Inactive)

Description

Currently, when the namespace LFSCK verifies the object's linkEA, it will check the linkEA without ldlm/dt lock firstly, if finds inconsistency, it will acquire the ldlm/dt lock on the object, then re-check the linkEA, if still invalid, it will repair the bad linkEA. For the system containing many inconsistent objects, such double-check mechanism is inefficient.

Be as some improvement, the LFSCK can make some prediction, for example: if former object contains bad linkEA, then when verifies current object, the namespace LFSCK can acquire the ldlm/dt lock on the object in advance; if the prediction is wrong, it will NOT take ldlm/dt lock in advance for next object.

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/14008/
Subject: LU-6350 lfsck: lock object based on prediction for bad linkEA
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: ad40feaee4f58399da8a048fa5342700b8aebc6c

[Gerrit Updater]

Fan Yong ([e-mail]) uploaded a new patch: http://review.whamcloud.com/14008
Subject: LU-6350 lfsck: lock object based on prediction for bad linkEA
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: df06416b562b05423522e1eee795906ad25064dc