LFSCK 4: improve LFSCK performance (LU-6361)

[LU-6350] LFSCK 4: lock the MDT-object based on prediction for preparing bad linkEA Created: 07/Mar/15  Updated: 01/May/15  Resolved: 01/May/15

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

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

Rank (Obsolete): 17772

 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   
Comment by Gerrit Updater [ 07/Mar/15 ]

Fan Yong (fan.yong@intel.com) 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

Comment by Gerrit Updater [ 01/May/15 ]

Oleg Drokin (oleg.drokin@intel.com) 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

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