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-3414 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 runs:<br/> <a href="http://maloo.whamcloud.com/test_sets/a06094ce-c83a-11e2-b8c5-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/a06094ce-c83a-11e2-b8c5-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/8ab52280-3536-11e2-918f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/8ab52280-3536-11e2-918f-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/36d646d4-2704-11e2-b04c-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/36d646d4-2704-11e2-b04c-52540035b04c</a></p> <p>The sub-test test_53e failed with the following error:</p> <blockquote> <p>test_53e failed with 2</p></blockquote> <p>Info required for matching: replay-single 53e</p> LU-3414

Test failure on test suite replay-single, subtest test_53e

Bug Minor Resolved Cannot Reproduce WC Triage Maloo Wed, 29 May 2013 17:22:39 +0000 Sun, 10 Oct 2021 22:20:05 +0000 Sun, 10 Oct 2021 22:20:05 +0000 Lustre 2.4.0 Lustre 2.7.0 0 6 <p>This looks like some kind of race in the test. The MDS console logs do not show the fail_loc being hit:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: == replay-single test 53e: |X| open reply while two MDC requests in flight == 10:59:03 Lustre: DEBUG MARKER: lctl set_param fail_loc=0x119 Lustre: DEBUG MARKER: lctl set_param fail_loc=0 Lustre: DEBUG MARKER: replay-single test_53e: @@@@@@ FAIL: test_53e failed with 2 </pre> </div></div> <p>while passing tests show the fail_loc is being hit:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: == replay-single test 53e: |X| open reply while two MDC requests in flight == 04:01:46 Lustre: DEBUG MARKER: lctl set_param fail_loc=0x119 Lustre: *** cfs_fail_loc=119, val=2147483648*** LustreError: target_send_reply_msg()) @@@ dropping reply req@ffff8800635ef000 x1436362426138208/t219043332110(0) o36-&gt;0e87a8e3-8c49-4757-2124-d93b92b79a2c@10.10.17.36@tcp:0/0 lens 488/448 DEBUG MARKER: lctl set_param fail_loc=0 </pre> </div></div> <p>Seems there is some code path that is bypassing this fail_loc. Oleg looked at the code, and the fail_loc is only being used indirectly (value stored, then checked later), so it is possible this is being overwritten in some rare cases?</p> <p>Hit this issue in interop test between 2.6.0 client and 2.7.0 server:</p> <p><a href="https://testing.hpdd.intel.com/test_sets/79a2ed54-bfc4-11e4-881f-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/79a2ed54-bfc4-11e4-881f-5254006e85c2</a></p> Development Rank 1|hzvs5r: Rank (Obsolete) 8459 Severity