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

sanity test_57b: MDC before 382704 != after 382680

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.10.0
    • None
    • Servers - 2.9.58, 3591, master
      Client - 2.9.0, build 22, b2_9
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Saurabh Tandan <saurabh.tandan@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sessions/f37f95be-4af5-11e7-b400-5254006e85c2.

      The sub-test test_57b failed with the following error:

      MDC before 382704 != after 382680
      

      test log:

      == sanity test 57b: default LOV EAs are stored inside large inodes =================================== 01:33:33 (1496712813)
      mcreating 100 files
      total: 100 creates in 0.07 seconds: 1478.94 creates/second
      Filesystem            1K-blocks   Used Available Use% Mounted on
      10.2.4.49@tcp:/lustre    991128 493192    429096  54% /mnt/lustre
      opening files to create objects/EAs
      Filesystem            1K-blocks   Used Available Use% Mounted on
      10.2.4.49@tcp:/lustre    991128 493192    429096  54% /mnt/lustre
       sanity test_57b: @@@@@@ FAIL: MDC before 382704 != after 382680 
      

      This issue is seen only during rolling upgrade/downgrade testing. Checked results for interop testing but this issue didn't occured.

      Other results with same issue.
      https://testing.hpdd.intel.com/test_sessions/6729ebe2-4af9-11e7-91f4-5254006e85c2
      https://testing.hpdd.intel.com/sub_tests/ebfa335c-4b05-11e7-bc6c-5254006e85c2

      Attachments

        Issue Links

          Activity

            [LU-9661] sanity test_57b: MDC before 382704 != after 382680
            yujian Jian Yu added a comment -

            The test script will be improved in LU-9677.

            yujian Jian Yu added a comment - The test script will be improved in LU-9677 .
            yujian Jian Yu added a comment -

            Thank you, Sarah.

            yujian Jian Yu added a comment - Thank you, Sarah.
            sarah Sarah Liu added a comment - - edited

            We should improve the test scripts with checking OST count to avoid this kind of failure. I will open a ticket- LU-9677

            sarah Sarah Liu added a comment - - edited We should improve the test scripts with checking OST count to avoid this kind of failure. I will open a ticket- LU-9677

            Yeah sure, I will do that.
            Thanks for looking into the issues.

            standan Saurabh Tandan (Inactive) added a comment - Yeah sure, I will do that. Thanks for looking into the issues.
            yujian Jian Yu added a comment -

            Thank you Saurabh.
            Could you please re-run the tests with 2 OSTs and larger device size? (many tests in the test session failed with out of space issue)

            yujian Jian Yu added a comment - Thank you Saurabh. Could you please re-run the tests with 2 OSTs and larger device size? (many tests in the test session failed with out of space issue)

            I don't have them on vms and yes you are right may be that can be the issue. And I will make sure I use 2 OSTs .

            standan Saurabh Tandan (Inactive) added a comment - I don't have them on vms and yes you are right may be that can be the issue. And I will make sure I use 2 OSTs .
            yujian Jian Yu added a comment -

            BTW, could you please run the tests with at least 2 OSTs in the future so as to avoid some configuration test failures?

            yujian Jian Yu added a comment - BTW, could you please run the tests with at least 2 OSTs in the future so as to avoid some configuration test failures?

            People

              yujian Jian Yu
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: