Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-6361 LFSCK 4: improve LFSCK performance
  3. LU-1453

LFSCK 4: Improve OI scrub trigger strategy: do not trigger urgent OI scrub on the whole system if only few inconsistent OI entries are found

Details

    • Technical task
    • Resolution: Fixed
    • Critical
    • Lustre 2.7.0, Lustre 2.5.4
    • Lustre 2.7.0, Lustre 2.5.3
    • 10228

    Description

      Generally, scanning the whole device for OI scrub routine check may take a long time. If the whole system only contains a few bad OI mappings, then it is not prudent to trigger OI scrub automatically with full speed when bad OI mapping is auto-detected. Instead, We should make the OI scrub to fix the found bad OI mappings only, and if more and more bad OI mappings are found that exceeds some given threshold, the OI scrub will run with full speed to scan whole device. The threshold of bad OI mappings that will trigger a complete scan can be adjusted via a proc interface.

      Attachments

        Issue Links

          Activity

            [LU-1453] LFSCK 4: Improve OI scrub trigger strategy: do not trigger urgent OI scrub on the whole system if only few inconsistent OI entries are found
            yong.fan nasf (Inactive) made changes -
            Parent New: LU-6361 [ 29081 ]
            Issue Type Original: Improvement [ 4 ] New: Technical task [ 7 ]
            pjones Peter Jones made changes -
            Labels Original: HB LFSCK mq115 New: HB LFSCK

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13021/
            Subject: LU-1453 tests: scrub interoperability issues with master
            Project: fs/lustre-release
            Branch: b2_5
            Current Patch Set:
            Commit: e677ff40708dae0b216df9e6316227effe134de3

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13021/ Subject: LU-1453 tests: scrub interoperability issues with master Project: fs/lustre-release Branch: b2_5 Current Patch Set: Commit: e677ff40708dae0b216df9e6316227effe134de3
            pjones Peter Jones made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
            pjones Peter Jones added a comment -

            Landed for 2.7. Will track 2.5.x landing separately

            pjones Peter Jones added a comment - Landed for 2.7. Will track 2.5.x landing separately
            adilger Andreas Dilger made changes -
            Labels Original: HB LFSCK New: HB LFSCK mq115

            Although the patch 12958 has been landed to master, we still need the patch 13021 on b2_5 to avoid interoperability issues.

            yong.fan nasf (Inactive) added a comment - Although the patch 12958 has been landed to master, we still need the patch 13021 on b2_5 to avoid interoperability issues.
            yong.fan nasf (Inactive) made changes -
            Fix Version/s New: Lustre 2.5.4 [ 11190 ]
            yong.fan nasf (Inactive) made changes -
            Affects Version/s New: Lustre 2.5.3 [ 11100 ]

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/12958/
            Subject: LU-1453 scrub: rename confused name full_scrub_speed
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 2d3d4525b1ac6697b5df207400801c4399d20378

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/12958/ Subject: LU-1453 scrub: rename confused name full_scrub_speed Project: fs/lustre-release Branch: master Current Patch Set: Commit: 2d3d4525b1ac6697b5df207400801c4399d20378

            People

              yong.fan nasf (Inactive)
              yong.fan nasf (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: