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-1753 Lustre <p>This issue was created by maloo for bobijam &lt;bobijam@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/d1a72d3c-d84d-11e1-b8ea-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/d1a72d3c-d84d-11e1-b8ea-52540035b04c</a>.</p> <p>The sub-test test_118i failed with the following error:</p> <blockquote> <p>got error, but should be not, rc=5</p></blockquote> <p>Info required for matching: sanity 118i</p> LU-1753

Test failure on test suite sanity, subtest test_118i

Bug Minor Resolved Won't Fix Hongchao Zhang Maloo Wed, 15 Aug 2012 21:16:08 +0000 Thu, 7 Jan 2016 23:51:42 +0000 Thu, 7 Jan 2016 23:51:42 +0000 Lustre 2.3.0 Lustre 2.4.0 Lustre 2.4.0 0 7 <p>another hit at <a href="https://maloo.whamcloud.com/test_sets/63bf779a-e719-11e1-ac43-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/63bf779a-e719-11e1-ac43-52540035b04c</a></p> <p>18:15:57:Lustre: DEBUG MARKER: == sanity test 118i: Fix error before timeout in recoverable error ============ 18:15:55 (1345338955)<br/> 18:16:08:LustreError: 11-0: an error occurred while communicating with 10.10.4.183@tcp. The ost_write operation failed with -5<br/> 18:16:08:LustreError: Skipped 4 previous similar messages<br/> 18:16:08:LustreError: 2970:0:(osc_request.c:1926:brw_interpret()) lustre-OST0000-osc-ffff880077362400: too many resent retries for object: 941:0, rc = -5.<br/> 18:16:11:Lustre: DEBUG MARKER: sanity test_118i: @@@@@@ FAIL: got error, but should be not, rc=5</p> <p>Another instance:<br/> <a href="https://maloo.whamcloud.com/test_sets/42417a68-ef8f-11e1-bdf7-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/42417a68-ef8f-11e1-bdf7-52540035b04c</a></p> <p>Another failure instance:<br/> <a href="https://maloo.whamcloud.com/test_sets/284e4e2a-f1d7-11e1-87d6-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/284e4e2a-f1d7-11e1-87d6-52540035b04c</a></p> <p>This is failing fairly regularly, bumping priority.</p> <p>Another failure:</p> <p><a href="https://maloo.whamcloud.com/test_sets/c093ca76-f49c-11e1-b3b2-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/c093ca76-f49c-11e1-b3b2-52540035b04c</a></p> <p><a href="https://maloo.whamcloud.com/test_sets/97853650-fe7a-11e1-b4cd-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/97853650-fe7a-11e1-b4cd-52540035b04c</a></p> <p>Another instance:<br/> <a href="https://maloo.whamcloud.com/test_sets/aebdde24-01f6-11e2-bc4e-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/aebdde24-01f6-11e2-bc4e-52540035b04c</a></p> <p>Another instance:<br/> <a href="https://maloo.whamcloud.com/test_sets/7219f60c-020e-11e2-ab94-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/7219f60c-020e-11e2-ab94-52540035b04c</a></p> <p>Hongchao</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p><a href="https://maloo.whamcloud.com/test_sets/807ed662-0273-11e2-ab94-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/807ed662-0273-11e2-ab94-52540035b04c</a></p> <p>this issue is caused by the failure of "fail_loc" reset,</p> <p>e.g.<br/> <a href="https://maloo.whamcloud.com/test_sets/807ed662-0273-11e2-ab94-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/807ed662-0273-11e2-ab94-52540035b04c</a></p> <p>in debug log,</p> <p>test started at 1348039162<br/> fail_loc set to OBD_FAIL_OST_BRW_WRITE_BULK at 1348039163<br/> first ost_write failed for this fail_loc at 1348039168<br/> fail_loc reset to 0 at 1348039173<br/> last ost_write failed for this fail_loc at 1348039178<br/> test failed at 1348039179</p> <p>but in console log, the fail_loc is reset at 1348039179</p> <p>00:19:28:Lustre: DEBUG MARKER: lctl set_param fail_loc=0x20e<br/> 00:19:29:Lustre: *** cfs_fail_loc=20e, val=0***<br/> 00:19:40:Lustre: DEBUG MARKER: lctl set_param fail_loc=0<br/> 00:19:40:Lustre: DEBUG MARKER: /usr/sbin/lctl mark sanity test_118i: @@@@@@ FAIL: got error, but should be not, rc=5 </p> <p>is it related to the test framework?</p> <p>When you say test-framework do you mean the test-infrastructure that is Autotest/Maloo/Toro or the test-framework that forms part of Lustre itself.</p> <p>If the later, which I suspect you mean, then it should be fixed as part of Lustre.</p> <p>the patch is tracked at <a href="http://review.whamcloud.com/#change,4071" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4071</a></p> <p>Dropping priority as this is known to be a test issue only. We'll land the test correction to master and also to b2_3 if we have another RC</p> <p><a href="https://maloo.whamcloud.com/test_sets/c03bd93c-042e-11e2-aec7-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/c03bd93c-042e-11e2-aec7-52540035b04c</a></p> <p>Test issue only.<br/> ~ jfc.</p> Development Rank 1|hzv3jz: Rank (Obsolete) 4075 Severity