[LU-6861] sanity-scrub test 4a and 4b fail: Auto trigger full scrub unexpectedly Created: 16/Jul/15  Updated: 25/Jan/17  Resolved: 20/Jul/16

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.8.0
Fix Version/s: Lustre 2.9.0

Type: Bug Priority: Critical
Reporter: James Nunez (Inactive) Assignee: nasf (Inactive)
Resolution: Fixed Votes: 0
Labels: lfsck
Environment:

review-dne-part-2 in autotest


Issue Links:
Blocker
is blocking LU-6562 sanity-scrub looks for wrong paramete... Resolved
Related
is related to LU-6562 sanity-scrub looks for wrong paramete... Resolved
is related to LU-8416 sanity-scrub test_4c: Auto trigger fu... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 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



 Comments   
Comment by Gerrit Updater [ 27/Oct/15 ]

Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/16951
Subject: LU-6861 scrub: only trigger full OI scrub when necessary
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 8125ce578beb5e47d896cf21a9880bf45ad5711d

Comment by Gerrit Updater [ 14/Jun/16 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/16951/
Subject: LU-6861 scrub: only trigger full OI scrub when necessary
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 76b4684a576ea423561fafb5fdb5f6f762e6b3e0

Comment by Jian Yu [ 14/Jul/16 ]

The failure still occurred on master branch:
https://testing.hpdd.intel.com/test_sets/3781a2f8-492f-11e6-9f8e-5254006e85c2
https://testing.hpdd.intel.com/test_sets/93d41614-4932-11e6-a80f-5254006e85c2
https://testing.hpdd.intel.com/test_sets/53c936fa-48d6-11e6-8968-5254006e85c2

Comment by James Nunez (Inactive) [ 20/Jul/16 ]

I think the recent failures listed above are due to LU-8416 and not this ticket; the error messages are the same, but the test logs look different.

Comment by Andreas Dilger [ 20/Jul/16 ]

Closing this ticket after patch was landed, LU-8416 should be used for the new sanity-scrub 4b/4c failures.

Generated at Sat Feb 10 02:03:54 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.