Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-6361 LFSCK 4: improve LFSCK performance
  3. LU-6350

LFSCK 4: lock the MDT-object based on prediction for preparing bad linkEA

    Details

    • Type: Technical task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Lustre 2.8.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.

        Attachments

          Activity

            People

            • Assignee:
              yong.fan nasf (Inactive)
              Reporter:
              yong.fan nasf (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: