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

sanity-lfsck test_23b: (9) Fail to repair dangling name entry: 0

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Lustre 2.13.0, Lustre 2.14.0
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for nasf <fan.yong@intel.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/d32d2bc0-428c-11e8-b45c-52540065bddc

      Inject failure stub on MDT0 to simulate dangling name entry
      fail_val=130
      fail_loc=0x1621
      fail_val=0
      fail_loc=0
       - unlinked 0 (time 1573179943 ; total 0 ; last 0)
      total: 10 unlinks in 0 seconds: inf unlinks/second
      'ls' should fail because of dangling name entry
      Trigger namespace LFSCK to find out dangling name entry
      Started LFSCK on the device lustre-MDT0000: scrub namespace
       sanity-lfsck test_23b: @@@@@@ FAIL: (9) Fail to repair dangling name entry: 0 
      

      Attachments

        Issue Links

          Activity

            [LU-10922] sanity-lfsck test_23b: (9) Fail to repair dangling name entry: 0
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-13170 [ LU-13170 ]
            jamesanunez James Nunez (Inactive) made changes -
            Affects Version/s New: Lustre 2.14.0 [ 14490 ]
            adilger Andreas Dilger made changes -
            Link Original: This issue is related to LU-7113 [ LU-7113 ]
            adilger Andreas Dilger made changes -
            Link Original: This issue is related to LU-7429 [ LU-7429 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-7113 [ LU-7113 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-7113 [ LU-7113 ]
            jamesanunez James Nunez (Inactive) made changes -
            Remote Link New: This issue links to "Page (Whamcloud Community Wiki)" [ 24259 ]
            jamesanunez James Nunez (Inactive) made changes -
            Description Original: This issue was created by maloo for nasf <fan.yong@intel.com>

            This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/d32d2bc0-428c-11e8-b45c-52540065bddc

            {noformat}
            Inject failure stub on MDT0 to simulate dangling name entry
            fail_val=130
            fail_loc=0x1621
            fail_val=0
            fail_loc=0
             - unlinked 0 (time 1573179943 ; total 0 ; last 0)
            total: 10 unlinks in 0 seconds: inf unlinks/second
            'ls' should fail because of dangling name entry
            Trigger namespace LFSCK to find out dangling name entry
            Started LFSCK on the device lustre-MDT0000: scrub namespace
             sanity-lfsck test_23b: @@@@@@ FAIL: (9) Fail to repair dangling name entry: 0
            {noformat}
            New: This issue was created by maloo for nasf <fan.yong@intel.com>

            This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/d32d2bc0-428c-11e8-b45c-52540065bddc

            {noformat}
            Inject failure stub on MDT0 to simulate dangling name entry
            fail_val=130
            fail_loc=0x1621
            fail_val=0
            fail_loc=0
             - unlinked 0 (time 1573179943 ; total 0 ; last 0)
            total: 10 unlinks in 0 seconds: inf unlinks/second
            'ls' should fail because of dangling name entry
            Trigger namespace LFSCK to find out dangling name entry
            Started LFSCK on the device lustre-MDT0000: scrub namespace
             sanity-lfsck test_23b: @@@@@@ FAIL: (9) Fail to repair dangling name entry: 0
            {noformat}
            adilger Andreas Dilger made changes -
            Labels New: zfs
            adilger Andreas Dilger made changes -
            Description Original: This issue was created by maloo for nasf <fan.yong@intel.com>

            This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/d32d2bc0-428c-11e8-b45c-52540065bddc

            <<Please provide additional information about the failure here>>
            New: This issue was created by maloo for nasf <fan.yong@intel.com>

            This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/d32d2bc0-428c-11e8-b45c-52540065bddc

            {noformat}
            Inject failure stub on MDT0 to simulate dangling name entry
            fail_val=130
            fail_loc=0x1621
            fail_val=0
            fail_loc=0
             - unlinked 0 (time 1573179943 ; total 0 ; last 0)
            total: 10 unlinks in 0 seconds: inf unlinks/second
            'ls' should fail because of dangling name entry
            Trigger namespace LFSCK to find out dangling name entry
            Started LFSCK on the device lustre-MDT0000: scrub namespace
             sanity-lfsck test_23b: @@@@@@ FAIL: (9) Fail to repair dangling name entry: 0
            {noformat}

            People

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

              Dates

                Created:
                Updated: