Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: Lustre 2.2.0
    • Fix Version/s: Lustre 2.2.0, Lustre 2.1.2
    • Labels:
      None
    • Severity:
      3
    • Rank (Obsolete):
      4713

      Description

      One one of our MDS nodes, we see a pretty voluminous stream of "Object doesn't exist" messages from the mdt_getattr_name_lock() function, and the associated LU_OBJECT_DEBUG output.

      We looked at code briefly and suspect that this is a race between an unlink and a getattr, which would be completely normal and expected.

      So why does this message exist? Is the race being handled correctly?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bobijam Zhenyu Xu
                Reporter:
                morrone Christopher Morrone
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: