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-3726 Lustre <p>Current version of sanity-hsm has to be adapted to support running with MDSCOUNT &gt;= 2.<br/> This is a prerequirement to integrate HSM+DNE testing in sanity-hsm.</p> <p>We are currently working on it (we will provide a patch).</p> LU-3726

Adapt sanity-hsm to support MDSCOUNT >= 2

Technical task LU-3647 Major Resolved Fixed Bruno Faccini Thomas LEIBOVICI - CEA HSM patch Thu, 8 Aug 2013 10:59:06 +0000 Thu, 12 Dec 2013 00:38:05 +0000 Thu, 12 Dec 2013 00:38:05 +0000 Lustre 2.5.0 Lustre 2.6.0 Lustre 2.5.1 0 7 <p>Bruno</p> <p>Could you please take care of this patch when it arrives?</p> <p>Thanks</p> <p>Peter</p> <p>Here is the proposed patch for this change:<br/> <a href="http://review.whamcloud.com/7437" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7437</a></p> <p>I had to re-run auto-tests for the change due <a href="https://jira.whamcloud.com/browse/LU-1458" title="lustre-rsync-test test_2b: old lustre_rsync does not work with new llog_changelog_ext_rec remove changelog" class="issue-link" data-issue-key="LU-1458"><del>LU-1458</del></a> bug trigger during lustre-rsync-test/test_2b.</p> <p>The following change depends on this patch: <a href="http://review.whamcloud.com/#/c/7571/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/7571/</a> (DNE specific tests for HSM).</p> <p>I had to re-trigger auto-tests for both patches due to TEI-534 (aka no_root_squash for copy-tool back-end) related issue ...</p> <p>Thomas,</p> <p>Can you, as WangDi indicated, re-submit (+ re-base before ...) your change #7437/patch-set #3 with "Test-Parameters: mdtcount=2 mdscount=2" added in Commit-msg, to allow it being tested under DNE conditions.</p> <p>Thanks!</p> <p>Hello Thomas,</p> <p>Thanks to add the "Test-Parameters: mdtcount=2 mdscount=2" added in Commit-msg.</p> <p>But I also have an other request, in order to clarify the JIRA-Ticket&lt;-&gt;Gerrit-Change relationships, could it be possible that you change Commit-msg of <a href="http://review.whamcloud.com/7437" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7437</a> and refer to this ticket instead of <a href="https://jira.whamcloud.com/browse/LU-3561" title="Add a sanity test for HSM" class="issue-link" data-issue-key="LU-3561"><del>LU-3561</del></a> ??</p> <p>Thanks again and in advance for your help.</p> <p>This ticket is now referenced in the commit message for changes <a href="http://review.whamcloud.com/7437" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7437</a> and <a href="http://review.whamcloud.com/7571" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7571</a>.<br/> The following test parameters have also been set for both of them, as they only modify sanity-hsm.sh:<br/> "Test-Parameters: mdtcount=2 mdscount=2 testlist=sanity-hsm"</p> <p>Thanks Thomas !! That will greatly help to clarify and not to get Gerrit changes orphaned.</p> <p>sanity-hsm subtests test_301/test_302 failed during Change #7437 patch-set #8 auto-tests DNE session.</p> <p>sanity-hsm subtests test_302/test_400/test_401/test_403/test_404 failed during Change #7571 patch-set #7 auto-tests DNE-specifc session.</p> <p>Need to analyze Maloo errors reports.</p> <p>The auto-tests failures that experienced patch-set #8 of <a href="http://review.whamcloud.com/7437" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7437</a> under DNE conditions are not related to itself but are due to the issue addressed in <a href="https://jira.whamcloud.com/browse/LU-4093" title="sanity-hsm test_24d: wanted &#39;SUCCEED&#39; got &#39;WAITING&#39;" class="issue-link" data-issue-key="LU-4093"><del>LU-4093</del></a> where orphan HSM requests prevents others to start. And on the other hand, since this condition can clear itself during a test-suite, the sub-tests modified by this patch to become "DNE-aware" ran successfully !!</p> <p>Auto-tests failures of Change #7571 patch-set #7 are DNE-specific and I will provide an update about them soon.</p> <p>I spent some time looking at Change #7571 patch-set #7 failures and here are some ideas I got doing so :</p> <p> _ sub-test 302, error/msg "hsm_control state is not 'enabled' on mds2". Seems that not all the MDSs/MDTs are re-started/failed (ie, only $SINGLEMDS). Thus mds2 has still its CDT stopped due to last cdt_shutdown ? If yes, this means all MDSs/MDTs must be failed.</p> <p> _ sub-test 400, error/msg "request on 0x3c0000401:0x8e:0x0 is not SUCCEED on mds1". In this case, it seems that the HSM request did not arrive where it was expected for the test!! Thus some local+manual debug with the patch/build must occur to understand what happen.</p> <p> _ sub-test 401, error/msg "lfs hsm_archive" (with -EAGAIN). It may be a consequence of the fact CDT did not restart on mds2 since sub-test #302 ?? If not, again some local+manual debug with the patch/build must occur to understand what happen.…</p> <p> _ sub-tests 403, errr/msg "uuid 289ff266-f294-17cc-b407-fe2e0f15c9a0 not found in agent list on mds2". Again, it may be a consequence of the fact CDT did not restart on mds2 since sub-test #302 ?? And again, if not, some local+manual debug with the patch/build must occur to understand what happen.</p> <p> _ sub-tests 404, err/msg "request on 0x3c0000401:0x90:0x0 is not SUCCEED on mds1". The immediate WAITING status of the request can come from the specific problem this sub-test tracks or can be a consequence that max_requests has reached due to the failures just before. Thus, it may be also a consequence of the fact CDT did not restart on mds2 since sub-test #302 ???? And again, if not, some local+manual debug with the patch/build must occur to understand what happen.</p> <p>I will run these tests with a local config running patch/build to see if I am right.</p> <p>Got email discussion with Thomas and he agrees with me that Change #7571 patch-set #7 sub-tests 301/401/403/404 failures could come from the fact CDT on mds2 was not restarted because all MDTs have themselves not been failed+retarted (ie, not only $SINGLEMDS).</p> <p>Thus after re-basing change #7571 patch-set #7, I also added/changed sub-test test_302 to fail all MDSs/MDTs instead of only SINGLEMDS. This is patch-set #8.</p> <p>The patch <a href="http://review.whamcloud.com/7571" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7571</a> landed to master. There is an open bug <a href="https://jira.whamcloud.com/browse/LU-4375" title="Test failure on test suite sanity-hsm, subtest test_302" class="issue-link" data-issue-key="LU-4375"><del>LU-4375</del></a> tracking some failures in sanity-hsm on DNE which should be used to address those failures.</p> Related LU-4375 Development Rank 1|hzvxfz: Rank (Obsolete) 9595