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

sanity-lfsck test_18a: Expect 3 fixed on mds1, but got: 0

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Lustre 2.11.0
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for sarah_lw <wei3.liu@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/c8be9e2c-3f44-11e7-91f3-5254006e85c2.

      The sub-test test_18a failed with the following error:

      (6.1) Expect 3 fixed on mds1, but got: 0
      

      client console. This one looks like LU-7190 but it was landed long time ago.

      Inject failure, to make the MDT-object lost its layout EA
      CMD: trevis-52vm7 /usr/sbin/lctl set_param fail_loc=0x1615
      fail_loc=0x1615
      CMD: trevis-52vm7 /usr/sbin/lctl set_param fail_loc=0
      fail_loc=0
      The file size should be incorrect since layout EA is lost
      Trigger layout LFSCK on all devices to find out orphan OST-object
      CMD: trevis-52vm7 /usr/sbin/lctl lfsck_start -M lustre-MDT0000 -t layout -r -o
      Started LFSCK on the device lustre-MDT0000: scrub layout
      CMD: trevis-52vm7 /usr/sbin/lctl get_param -n 			mdd.lustre-MDT0000.lfsck_layout |
      			awk '/^status/ { print \$2 }'
      CMD: trevis-52vm7 /usr/sbin/lctl get_param -n 			mdd.lustre-MDT0000.lfsck_layout |
      			awk '/^status/ { print \$2 }'
      CMD: trevis-52vm8 /usr/sbin/lctl get_param -n obdfilter.lustre-OST0000.lfsck_layout
      CMD: trevis-52vm8 /usr/sbin/lctl get_param -n obdfilter.lustre-OST0001.lfsck_layout
      CMD: trevis-52vm7 /usr/sbin/lctl get_param -n mdd.lustre-MDT0000.lfsck_layout
       sanity-lfsck test_18a: @@@@@@ FAIL: (6.1) Expect 3 fixed on mds1, but got: 0 }
      

      Attachments

        Issue Links

          Activity

            [LU-9631] sanity-lfsck test_18a: Expect 3 fixed on mds1, but got: 0

            We haven't seen this test fail on master in over seven months. We are seeing a very similar error on the b2_10 branch. Opened LU-11909 to track the failure on b2_10.

            jamesanunez James Nunez (Inactive) added a comment - We haven't seen this test fail on master in over seven months. We are seeing a very similar error on the b2_10 branch. Opened LU-11909 to track the failure on b2_10.

            This looks very similar to a 2.10.51 sanity-lfsck failure:

            https://testing.hpdd.intel.com/test_sessions/b4f16675-0495-4452-87d4-761d1cf8da40

            sanity-lfsck test_20a: (4.1) Expect 9 fixed on mds1, but got: 13

            jcasper James Casper (Inactive) added a comment - This looks very similar to a 2.10.51 sanity-lfsck failure: https://testing.hpdd.intel.com/test_sessions/b4f16675-0495-4452-87d4-761d1cf8da40 sanity-lfsck test_20a: (4.1) Expect 9 fixed on mds1, but got: 13
            pjones Peter Jones added a comment - - edited

            side effect of earlier version of LU-9442 patch

            pjones Peter Jones added a comment - - edited side effect of earlier version of LU-9442 patch

            People

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

              Dates

                Created:
                Updated:
                Resolved: