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-2608 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/9ff8d8c0-5ae9-11e2-b205-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/9ff8d8c0-5ae9-11e2-b205-52540035b04c</a>.</p> <p>The sub-test test_100 failed with the following error:</p> <blockquote> <p>test_100 returned 1</p></blockquote> <p>I found many test failures with similar message : "FAIL: LBUG/LASSERT detected" during the ZFS OFED build testing, but cannot find related LBUG or ASSERTION info from dmesg or console logs.</p> LU-2608

Failure on test suite recovery-small test_100: FAIL: LBUG/LASSERT detected

Bug Blocker Resolved Fixed Nathaniel Clark Maloo HB zfs Sat, 12 Jan 2013 01:38:44 +0000 Mon, 22 Apr 2013 01:53:42 +0000 Wed, 13 Feb 2013 17:44:14 +0000 Lustre 2.4.0 Lustre 2.4.0 0 5 <p>similar error message:<br/> <a href="https://maloo.whamcloud.com/test_sets/9835100e-5ae9-11e2-b205-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/9835100e-5ae9-11e2-b205-52540035b04c</a></p> <p><a href="https://maloo.whamcloud.com/test_sets/05f6b8c0-5ae7-11e2-b205-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/05f6b8c0-5ae7-11e2-b205-52540035b04c</a> test_44c</p> <p>I just had a look in each of the test_log for all 3 test failures you indicated, and I think the "FAIL: LBUG/LASSERT detected" may be a false-positive induced by IB communications error during infos/msgs gather on remote nodes.</p> <p>Each time the log/errors sequence looks like :</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>..... Resetting fail_loc on all nodes...done. &lt; but sometimes with errors already ... &gt; pdsh@client-X: client-Y-ib: read: protocol failure: timed out &lt; at least for one node, but often multiples ... &gt; &lt;test&gt; &lt;subtest&gt;: @@@@@@ FAIL: LBUG/LASSERT detected Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:3938:error_noexit() = /usr/lib64/lustre/tests/test-framework.sh:3961:error() = /usr/lib64/lustre/tests/test-framework.sh:4205:run_one() = /usr/lib64/lustre/tests/test-framework.sh:4231:run_one_logged() = /usr/lib64/lustre/tests/test-framework.sh:4104:run_test() = /usr/lib64/lustre/tests/&lt;test&gt;.sh:1391:main() ..... </pre> </div></div> <p>So seems that return-values/failures from do_nodes() must be better checked in check_catastrophe().</p> <p><a href="http://review.whamcloud.com/5200" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5200</a></p> <p>Patch landed to master</p> Development Rank 1|hzvf3r: Rank (Obsolete) 6092 Severity