Details

    • Bug
    • Resolution: Fixed
    • Major
    • Lustre 2.13.0, Lustre 2.12.3
    • Lustre 2.13.0
    • Any lustre client
    • 3
    • 9223372036854775807

    Description

      In recent testing I have encounter cases were running lfs df never returns. Today I sat down to track down why it never returns. The reason is this loop never exits in showdf() in lfs.c.

      for (i = 0, state = stat->os_state; state != 0; i++)

      { ... }

      Attachments

        Activity

          [LU-12501] lfs df can never return

          Yes I tracked the issue Peter. Currently my test setup is all SSDs so I see this problem.

          simmonsja James A Simmons added a comment - Yes I tracked the issue Peter. Currently my test setup is all SSDs so I see this problem.

          James Simmons (uja.ornl@yahoo.com) uploaded a new patch: https://review.whamcloud.com/35403
          Subject: LU-12501 utils: stop showdf() endless loop
          Project: fs/lustre-release
          Branch: master
          Current Patch Set: 1
          Commit: eba159fd6d2b45689072cd59dff3c77af83c00aa

          gerrit Gerrit Updater added a comment - James Simmons (uja.ornl@yahoo.com) uploaded a new patch: https://review.whamcloud.com/35403 Subject: LU-12501 utils: stop showdf() endless loop Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: eba159fd6d2b45689072cd59dff3c77af83c00aa
          pjones Peter Jones added a comment -

          Does that mean that you are able to run git bisect to identify the commit that introduced the problem?

          pjones Peter Jones added a comment - Does that mean that you are able to run git bisect to identify the commit that introduced the problem?
          simmonsja James A Simmons added a comment - - edited

          The last couple of weeks  I started to see it. For some reason I see this all the time on our test bed.

          simmonsja James A Simmons added a comment - - edited The last couple of weeks  I started to see it. For some reason I see this all the time on our test bed.

          James,

          When do you see this problem?  It's clearly not all the time, as we don't see it in our testing.

          pfarrell Patrick Farrell (Inactive) added a comment - James, When do you see this problem?  It's clearly not all the time, as we don't see it in our testing.
          pjones Peter Jones added a comment -

          James

          Any idea of when this problem first appeared?

          Peter

          pjones Peter Jones added a comment - James Any idea of when this problem first appeared? Peter

          People

            adilger Andreas Dilger
            simmonsja James A Simmons
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: