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

sanity test_69: test failed to respond and timed out

Details

    • Bug
    • Resolution: Not a Bug
    • Minor
    • None
    • Lustre 2.8.0
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/d0419a58-f2f4-11e4-9186-5254006e85c2.

      The sub-test test_69 failed with the following error:

      test failed to respond and timed out

      after none for years 4 instances of this in the last day. either a TEI problem or something bad recently in master.

      more instances:
      https://testing.hpdd.intel.com/test_sets/59ebe636-f2f1-11e4-acf4-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/dd96b002-f318-11e4-a51d-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/c057d9aa-f31b-11e4-9186-5254006e85c2

      Info required for matching: sanity 69

      Attachments

        Issue Links

          is blocking

          Improvement - An improvement or enhancement to an existing feature or task. LU-6260 more support for 3.16 linux kernel

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            [LU-6567] sanity test_69: test failed to respond and timed out
            pjones Peter Jones added a comment -

            ok thanks James

            pjones Peter Jones added a comment - ok thanks James
            simmonsja James A Simmons added a comment -

            The latest version of this patch no longer fails this test. We can close this ticket.

            simmonsja James A Simmons added a comment - The latest version of this patch no longer fails this test. We can close this ticket.
            simmonsja James A Simmons added a comment -

            It is a real failure. I will start to look at it tomorrow to resolve the bug.

            simmonsja James A Simmons added a comment - It is a real failure. I will start to look at it tomorrow to resolve the bug.
            adilger Andreas Dilger added a comment -

            I see in these test failures in the client console logs:

            09:24:13:LustreError: 28548:0:(rw26.c:260:ll_direct_rw_pages()) ASSERTION( !(file_offset & (page_size - 1)) ) failed: 
09:24:13:LustreError: 28548:0:(rw26.c:260:ll_direct_rw_pages()) LBUG
            adilger Andreas Dilger added a comment - I see in these test failures in the client console logs: 09:24:13:LustreError: 28548:0:(rw26.c:260:ll_direct_rw_pages()) ASSERTION( !(file_offset & (page_size - 1)) ) failed: 09:24:13:LustreError: 28548:0:(rw26.c:260:ll_direct_rw_pages()) LBUG
            adilger Andreas Dilger added a comment -

            All of these failures are on the patch series starting with http://review.whamcloud.com/14665 "LU-6260 llite: add support for direct IO api changes" so it appears this is a regression in that patch.

            adilger Andreas Dilger added a comment - All of these failures are on the patch series starting with http://review.whamcloud.com/14665 " LU-6260 llite: add support for direct IO api changes" so it appears this is a regression in that patch.
            jhammond John Hammond added a comment -

            I think this is due to NFS issues on shadow.

            jhammond John Hammond added a comment - I think this is due to NFS issues on shadow.

            People

              wc-triage WC Triage
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: