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-4545 Lustre <p>This issue was created by maloo for Nathaniel Clark &lt;nathaniel.l.clark@intel.com&gt;</p> <p>This issue relates to the following test suite run:<br/> <a href="http://maloo.whamcloud.com/test_sets/7976264e-650b-11e3-b82f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/7976264e-650b-11e3-b82f-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/64947b40-858b-11e3-a2cb-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/64947b40-858b-11e3-a2cb-52540035b04c</a></p> <p>The sub-test test_223a failed with the following error:</p> <blockquote> <p>request on 0x200000402:0x13f:0x0 is not SUCCEED on mds1</p></blockquote> <p>Info required for matching: sanity-hsm 223a</p> LU-4545

Test failure sanity-hsm test_223a: request on 0x200000402:0x13f:0x0 is not SUCCEED

Bug Blocker Resolved Fixed Bruno Faccini Maloo HSM patch Mon, 27 Jan 2014 15:11:26 +0000 Wed, 9 Apr 2014 17:34:15 +0000 Wed, 12 Mar 2014 15:14:39 +0000 Lustre 2.6.0 Lustre 2.5.1 Lustre 2.6.0 Lustre 2.5.2 0 12 <p>While testing patch <a href="http://review.whamcloud.com/9006" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9006</a> on Lustre b2_5 branch, the same failure occurred:<br/> <a href="https://maloo.whamcloud.com/test_sets/ca227340-886a-11e3-af42-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/ca227340-886a-11e3-af42-52540035b04c</a></p> <p>Another failure instance:</p> <p><a href="https://maloo.whamcloud.com/test_sets/0cad3fe2-93ce-11e3-b8a9-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/0cad3fe2-93ce-11e3-b8a9-52540035b04c</a></p> <p>An other at <a href="https://maloo.whamcloud.com/test_sets/4af8947e-9458-11e3-9ec0-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/4af8947e-9458-11e3-9ec0-52540035b04c</a>.</p> <p><a href="https://maloo.whamcloud.com/test_sets/7976264e-650b-11e3-b82f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/7976264e-650b-11e3-b82f-52540035b04c</a><br/> is probably related to a ENOSPC error.</p> <p>But the 4 others have a similar pattern.<br/> In most cases, RESTORE is started by copytool, and, when doing the first PROGRESS, copytool realizes this operation was canceled and so abort its operation. It notifies this to coordinator in (<tt>ct_fini()</tt>).<br/> But this is a little bit racy. For some cases, copytool will not have enough time to really start the restore. It will call <tt>ct_restore_begin()</tt>, which will send a PROGRESS to coordinator which will return <tt>-ECANCELED</tt>.<br/> <tt>ct_restore()</tt> does not handle this error case the same way if it appears so soon. <tt>ct_fini()</tt> is not called in this case because <tt>hpc</tt> is NULL (<tt>lustre/utils/lhsmtool_posix.c:1140</tt>)</p> <p>In real life, this is not a real problem. The request will be really canceled and this is what is expected. The cancel request itself will stay STARTED in action llog until eventually it timeouts. This request is expected to be succeeded if copytool really acknowledge the cancel operation, which it does not do in this case.</p> <p>The following patch should prevent that from happening by forcing the CT to report progress/error.</p> <p><a href="http://review.whamcloud.com/9310" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9310</a></p> <p>another one:<br/> <a href="https://maloo.whamcloud.com/test_sets/1ae74dec-99b3-11e3-83d7-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/1ae74dec-99b3-11e3-83d7-52540035b04c</a></p> <p>Bruno</p> <p>Could you please take care of this patch?</p> <p>Thanks</p> <p>Peter</p> <p>After some unrelated errors and re-trigger, patch successfully passed auto-tests. Only waiting for mre reviewers feedback now.</p> <p>Patch landed to Master. Will be back ported to b2_5</p> <p>Patch for b2_5 at <a href="http://review.whamcloud.com/#/c/9708/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/9708/</a></p> <p><a href="http://review.whamcloud.com/#/c/9708/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/9708/</a> landed to b2_5.</p> Development Rank 1|hzwdo7: Rank (Obsolete) 12423 Severity