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

lustre client hangs on possible imp_lock deadlock

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Critical
    • None
    • Lustre 2.4.2
    • Sequoia, 2.6.32-431.23.3.1chaos, github.com/chaos/lustre
    • 3
    • 16049

    Description

      The node becomes unresponsive to users and the lustre client appears to be hung after being evicted by the MDT. The node remains responsive to SysRq. After crashing the node, it boots and mounts lustre successfully.

      The symptoms develop as follows:

      First the node starts reporting connection lost/connection restored
      notices for an OST (same one repeatedly). Then the node reports it has
      been evicted by the MDT. There are then a series of failure messages
      that appear to be the normal consequence of the eviction.

      We then start seeing "spinning too long" messages from
      ptlrpc_check_set() within the ptlrpcd_rcv task, and the kernel starts
      reporting soft lockups on tasks ptlrpcd* and ll_ping. The node becomes
      unresponsive to everything other than SysRq. The operators then crash
      the node, and it comes up and mounts lustre successfully.

      Attachments

        Activity

          [LU-5720] lustre client hangs on possible imp_lock deadlock
          pjones Peter Jones added a comment -

          ok. Thanks Olaf.

          pjones Peter Jones added a comment - ok. Thanks Olaf.
          ofaaland Olaf Faaland added a comment - - edited

          After rebuilding the kernel with CONFIG_DEBUG_SPINLOCK enabled, we stopped seeing the problem. You can close it. We won't have any additional information to help track it down.

          ofaaland Olaf Faaland added a comment - - edited After rebuilding the kernel with CONFIG_DEBUG_SPINLOCK enabled, we stopped seeing the problem. You can close it. We won't have any additional information to help track it down.
          ofaaland Olaf Faaland added a comment -

          I will check and get back to you.

          ofaaland Olaf Faaland added a comment - I will check and get back to you.

          Any further report on this issue? Can we close it?

          niu Niu Yawei (Inactive) added a comment - Any further report on this issue? Can we close it?
          green Oleg Drokin added a comment -

          Ok.
          Lat time the problem did go away magically I believe.
          Please keep us informed about occurences (or lack of them) with the spinlock-debug enabled kernel.

          green Oleg Drokin added a comment - Ok. Lat time the problem did go away magically I believe. Please keep us informed about occurences (or lack of them) with the spinlock-debug enabled kernel.
          ofaaland Olaf Faaland added a comment - - edited

          This is a current problem. We are hitting it intermittently. We have 6 lac nodes on sequoia, most recent incident was last Tuesday.

          At the end of today we plan to install the kernel that has spinlock debug turned on, so we will have more information next time it happens (if it doesn't magically go away with the kernel change).

          ofaaland Olaf Faaland added a comment - - edited This is a current problem. We are hitting it intermittently. We have 6 lac nodes on sequoia, most recent incident was last Tuesday. At the end of today we plan to install the kernel that has spinlock debug turned on, so we will have more information next time it happens (if it doesn't magically go away with the kernel change).
          green Oleg Drokin added a comment -

          Hm, I see. This is not really promising then.

          Is this still something that hits for you regularly now or is this like in the past hit a few times and then stopped?

          green Oleg Drokin added a comment - Hm, I see. This is not really promising then. Is this still something that hits for you regularly now or is this like in the past hit a few times and then stopped?

          People

            niu Niu Yawei (Inactive)
            ofaaland Olaf Faaland
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: