[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

• Type: Technical task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Lustre 2.7.0, Lustre 2.5.3
• Fix Version/s: Lustre 2.7.0, Lustre 2.5.4
• Labels: HB LFSCK
• Assignee: nasf (Inactive)
• Reporter: nasf (Inactive)

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.

Issue Links

• is related to: LU-6012 sanity-scrub test_6 test_7 test_8 test_9 test_10a: expected 'inconsistent' but got 'inconsistent,auto'