[LU-6861] sanity-scrub test 4a and 4b fail: Auto trigger full scrub unexpectedly

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.9.0
• Affects Version/s: Lustre 2.8.0
• Labels: lfsck
• Environment: review-dne-part-2 in autotest
• Severity: 3
• Assignee: nasf (Inactive)
• Reporter: James Nunez (Inactive)

Description

The patch for LU-6562 at http://review.whamcloud.com/#/c/14660/ corrected sanity-scrub tests 4a, 4b, and 4c to correctly look for the ‘prior updated’ parameter in the OI scrub output. Correcting this triggered a failure, printing the values of prior_updated before (updated0) and after the scrub_check_* routines and, for 4b,, we see:

updated0[1] = 3
updated0[2] = 0
updated0[3] = 0
updated0[4] = 0
updated1[1] = 4
updated1[2] = 0
sanity-scrub test_4b: @@@@@@ FAIL: (12) Auto trigger full scrub unexpectedly 

From the comments in LU-6562, this output is unexpected.

Logs for sanity-scrub test 4b and 4c failures at: https://testing.hpdd.intel.com/test_sets/ae20b066-f2d2-11e4-aad2-5254006e85c2

Issue Links

• is blocking: LU-6562 sanity-scrub looks for wrong parameters in osd-ldisfs.*MDT*.oi_scrub
• is related to: LU-6562 sanity-scrub looks for wrong parameters in osd-ldisfs.*MDT*.oi_scrub
• is related to: LU-8416 sanity-scrub test_4c: Auto trigger full scrub unexpectedly