https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6562 Lustre <p>In sanity-scrub, tests 4a, 4b, and 4c look for ‘sf_items_updated_prior’ in osd-ldiskfs.*.oi_scrub on each MDT, but there is no ‘sf_items_updated_prior’. These tests should be looking for the value of ‘prior_updated’.</p> <p>I will upload a patch for this.</p> LU-6562

sanity-scrub looks for wrong parameters in osd-ldisfs.*MDT*.oi_scrub

Bug Minor Resolved Duplicate James Nunez James Nunez patch tests Mon, 4 May 2015 15:43:54 +0000 Thu, 17 Dec 2015 18:52:12 +0000 Thu, 17 Dec 2015 18:52:12 +0000 Lustre 2.8.0 0 5 <p>James Nunez (james.a.nunez@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/14660" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14660</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6562" title="sanity-scrub looks for wrong parameters in osd-ldisfs.*MDT*.oi_scrub" class="issue-link" data-issue-key="LU-6562"><del>LU-6562</del></a> tests: sanity-scrub parse 'prior_updated'<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 6ffdef88bb57e2e26847e317504dc4f310d744dc</p> <p>Now that I've changed tests 4b and 4c to look for "prior_updated" in the osd-ldiskfs.*.oi_scrub parameters, these tests reliably fail in a DNE set up. I can reproduce this on my cluster with 2 MDSs with 2 MDTs each and in our autotest VMs:<br/> <a href="https://testing.hpdd.intel.com/test_sets/ae20b066-f2d2-11e4-aad2-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/ae20b066-f2d2-11e4-aad2-5254006e85c2</a></p> <p>The failure is:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>FAIL: (12) Auto trigger full scrub unexpectedly </pre> </div></div> <p>I've printed the values of prior_updated before (updated0) and after the scrub_check_* routines and, for 4b, I see:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>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 </pre> </div></div> <p>The test that fails is the check that updated0<span class="error">&#91;i&#93;</span> is strictly less than updated1<span class="error">&#91;i&#93;</span>.</p> <p>Di or Fan Yong, <br/> Should this test be changed to look for full scrub on only the first MDT or should the check be changed from less than to less than or equal to? Or is there an actual error and the test should remain as it is?</p> <p>Thank you.</p> <blockquote> <p>updated0<span class="error">&#91;1&#93;</span> = 3<br/> updated0<span class="error">&#91;2&#93;</span> = 0<br/> updated0<span class="error">&#91;3&#93;</span> = 0<br/> updated0<span class="error">&#91;4&#93;</span> = 0<br/> updated1<span class="error">&#91;1&#93;</span> = 4<br/> updated1<span class="error">&#91;2&#93;</span> = 0<br/> sanity-scrub test_4b: @@@@@@ FAIL: (12) Auto trigger full scrub unexpectedly </p></blockquote> <p>That is unexpected. For test_4b, there should be OI scrub updating on every MDT, so update0<span class="error">&#91;x&#93;</span> should not be zero. Your scripts fixing about replacing "sf_items_updated_prior" with "updated_prior" is right. We need more investigation for the check failure.</p> <p>Logs for a sanity-scrub test 4b and 4c failure is at: <a href="https://testing.hpdd.intel.com/test_sets/ae20b066-f2d2-11e4-aad2-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/ae20b066-f2d2-11e4-aad2-5254006e85c2</a></p> <p>Opened <a href="https://jira.whamcloud.com/browse/LU-6861" title="sanity-scrub test 4a and 4b fail: Auto trigger full scrub unexpectedly" class="issue-link" data-issue-key="LU-6861"><del>LU-6861</del></a> to track the bug that this patch uncovered.</p> <p>Patch <a href="http://review.whamcloud.com/#/c/14660/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/14660/</a> was abandoned because the modification was incorporated into patch <a href="http://review.whamcloud.com/#/c/16951/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/16951/</a> for ticket <a href="https://jira.whamcloud.com/browse/LU-6861" title="sanity-scrub test 4a and 4b fail: Auto trigger full scrub unexpectedly" class="issue-link" data-issue-key="LU-6861"><del>LU-6861</del></a>. This ticket can be closed when patch 16951 lands.</p> <p>Closing this ticket since it will be fixed by <a href="https://jira.whamcloud.com/browse/LU-6861" title="sanity-scrub test 4a and 4b fail: Auto trigger full scrub unexpectedly" class="issue-link" data-issue-key="LU-6861"><del>LU-6861</del></a> patch <a href="http://review.whamcloud.com/16951" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16951</a> and there isn't much value keeping this ticket open anymore.</p> Blocker LU-6861 Related LU-6861 Development Rank 1|hzxcgf: Rank (Obsolete) 9223372036854775807 Severity