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

sanity test_56ra: should send 14 glimpse RPCs to OST

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Olaf Faaland <faaland1@llnl.gov>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/0bfa6acb-7f2a-4241-8b90-053dfdf0aabe

      test_56ra failed with the following error:

      '/usr/bin/lfs find -size 5 -type f /mnt/lustre/d56ra.sanity' should send 14 glimpse RPCs to OST
      

      The test had executed an "lfs find -size 5 -type f" and expected ldlm_glimpse_enqueue in $OSC.$OSC.stats to increase by 14 during that time. During the test it increased by 15.

      All nodes were running b2_12, centos 7, kernel 3.10.0-1062.9.1.el7.x86_64. The console log did not include any error messages.

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity test_56ra - '/usr/bin/lfs find -size 5 -type f /mnt/lustre/d56ra.sanity' should send 14 glimpse RPCs to OST

      Attachments

        Issue Links

          Activity

            [LU-13378] sanity test_56ra: should send 14 glimpse RPCs to OST

            Looks like a duplicate of LU-13017.

            The easiest way to find known duplicates is to use https://testing.whamcloud.com/sub_tests/query to search for recent FAIL results for that subtest (e.g. past week, or past 4 weeks if none appear).

            If your patch is the only one that has failed in the past 4 weeks (as seen by the Gerrit change and LU ticket numbers), then the problem is likely in your patch. If there are lots of other issues with the same failure (subtest number and error message), then "Associate" the failure to that LU issue and retest. Only if there are a bunch of failures for the same subtest that don't have any bug assigned, and no similar ticket exists in Jira is a new issue needed.

            adilger Andreas Dilger added a comment - Looks like a duplicate of LU-13017 . The easiest way to find known duplicates is to use https://testing.whamcloud.com/sub_tests/query to search for recent FAIL results for that subtest (e.g. past week, or past 4 weeks if none appear). If your patch is the only one that has failed in the past 4 weeks (as seen by the Gerrit change and LU ticket numbers), then the problem is likely in your patch. If there are lots of other issues with the same failure (subtest number and error message), then "Associate" the failure to that LU issue and retest. Only if there are a bunch of failures for the same subtest that don't have any bug assigned, and no similar ticket exists in Jira is a new issue needed.

            People

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

              Dates

                Created:
                Updated:
                Resolved: