Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-3280

when lock->l_lvb_data is freed, LDLM_FL_LVB_READY is not cleared

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • Lustre 2.4.0
    • Lustre 2.4.0
    • 3
    • 8117

    Description

      in ldlm_lock_decref_internal() when l_lvb_data is freed to reduce memory consumption, LDLM_FL_LVB_READY is not cleared, so later when the lock is reused lvb is never updated. We hit this case after a restore in HSM.
      Patch will follow

      Attachments

        Activity

          [LU-3280] when lock->l_lvb_data is freed, LDLM_FL_LVB_READY is not cleared

          Closing ticket as patch landed to master. If more work is needed, please let me know and I'll reopen.

          jlevi Jodi Levi (Inactive) added a comment - Closing ticket as patch landed to master. If more work is needed, please let me know and I'll reopen.

          Yes, it will affect normal usage of 2.4 because the inode can be purged by kernel but the corresponding layout lock can still exist. We should include this in 2.4.

          jay Jinshan Xiong (Inactive) added a comment - Yes, it will affect normal usage of 2.4 because the inode can be purged by kernel but the corresponding layout lock can still exist. We should include this in 2.4.

          Jinshan, can you please take a look at this bug and see whether this will affect normal usage in 2.4.0, or does it only affect HSM?

          adilger Andreas Dilger added a comment - Jinshan, can you please take a look at this bug and see whether this will affect normal usage in 2.4.0, or does it only affect HSM?
          jcl jacques-charles lafoucriere added a comment - patch at http://review.whamcloud.com/6268

          People

            jay Jinshan Xiong (Inactive)
            cealustre CEA
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: