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

:mdt_intent_reint()) ASSERTION( rc == 0 ) failed: Error occurred but lock handle is still in use, rc = -116

Details

    • Bug
    • Resolution: Done
    • Critical
    • None
    • Lustre 2.5.3
    • None
    • 3
    • 9223372036854775807

    Description

      Hit LBUG on mdt. See attached Console and Process Traces.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. LU-5934 mdt_intent_reint()) ASSERTION( rc == 0 ) failed: Error occurred but lock handle is still in use, rc = -2

          • Major - Major loss of function.
          • Resolved

          Activity

            [LU-6706] :mdt_intent_reint()) ASSERTION( rc == 0 ) failed: Error occurred but lock handle is still in use, rc = -116
            jfc John Fuchs-Chesney (Inactive) added a comment -

            Thanks Mahmoud.
            ~ jfc.

            jfc John Fuchs-Chesney (Inactive) added a comment - Thanks Mahmoud. ~ jfc.
            mhanafi Mahmoud Hanafi added a comment -

            Please close this case

            mhanafi Mahmoud Hanafi added a comment - Please close this case
            jaylan Jay Lan (Inactive) added a comment - - edited

            Is there is 2.5.4 release going on? I do not see activity under b2_5 branch. Do I need
            a special arrangement to access the code?

            jaylan Jay Lan (Inactive) added a comment - - edited Is there is 2.5.4 release going on? I do not see activity under b2_5 branch. Do I need a special arrangement to access the code?
            adilger Andreas Dilger added a comment -

            Hello Mahmoud,
            I was looking at the mdtConsoleLogs file, but the LASSERT message didn't produce a stack trace because it entered kdb. It would have been useful to provide a stack backtrace. It would also be more useful if the backtrace and bug description was in the initial bug Description field rather than only in an attachment, since that makes it easier to review, prioritize, and assign this ticket, and later search for it if needed.

            That said, it appears that this problem is a duplicate of LU-5934, which was fixed for the 2.5.4 release, but it isn't 100% clear without a stack trace.

            adilger Andreas Dilger added a comment - Hello Mahmoud, I was looking at the mdtConsoleLogs file, but the LASSERT message didn't produce a stack trace because it entered kdb . It would have been useful to provide a stack backtrace. It would also be more useful if the backtrace and bug description was in the initial bug Description field rather than only in an attachment, since that makes it easier to review, prioritize, and assign this ticket, and later search for it if needed. That said, it appears that this problem is a duplicate of LU-5934 , which was fixed for the 2.5.4 release, but it isn't 100% clear without a stack trace.
            mhanafi Mahmoud Hanafi added a comment -

            I did see that but wanted to confirm that it is the same.

            mhanafi Mahmoud Hanafi added a comment - I did see that but wanted to confirm that it is the same.
            pjones Peter Jones added a comment -

            Mahmoud

            This appears to be a duplicate of LU-5934 which is fixed in the 2.5.4 FE release

            Peter

            pjones Peter Jones added a comment - Mahmoud This appears to be a duplicate of LU-5934 which is fixed in the 2.5.4 FE release Peter

            People

              bogl Bob Glossman (Inactive)
              mhanafi Mahmoud Hanafi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: