Details

    • Technical task
    • Resolution: Fixed
    • Critical
    • Lustre 2.6.0
    • None
    • None
    • 9107

    Description

      There are two cases for dangling reference:

      1. A formerly allocated OST-object is lost. The LFSCK will allocate new OST-object with the specified object external FID and initialize it with the given parent MDT-object FID and owner attributes. Although the new created OST-object is initialized, the SUID + SGID mode will be kept, which will be dropped by the first modification RPC, like write/punch/setattr. Then we can distinguish whether the new create OST-object has been modified or not.
      2. The OST-object is there, but it is not initialized, and without SUID + SGID mode set. Then the LFSCK will initialize it with the given parent MDT-object FID and owner attributes.

      Attachments

        Activity

          [LU-3590] Repair the file which MDT-object has dangling reference

          The patch has been landed to master.

          yong.fan nasf (Inactive) added a comment - The patch has been landed to master.
          yong.fan nasf (Inactive) added a comment - This is the patch: http://review.whamcloud.com/#/c/7517/

          People

            yong.fan nasf (Inactive)
            rhenwood Richard Henwood (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: