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-5571 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="https://testing.hpdd.intel.com/test_sets/c07fa6c6-189a-11e4-bd79-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/c07fa6c6-189a-11e4-bd79-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/fe33929a-2fe0-11e4-957a-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/fe33929a-2fe0-11e4-957a-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/fe22e280-3146-11e4-b503-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/fe22e280-3146-11e4-b503-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/199c6a08-31d9-11e4-a833-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/199c6a08-31d9-11e4-a833-5254006e85c2</a></p> <p>The sub-test test_13 failed with the following error:</p> <blockquote> <p>(2) unexpected status</p></blockquote> <p>Info required for matching: sanity-lfsck 13</p> LU-5571

Test failure sanity-lfsck test_13: (2) unexpected status

Bug Critical Resolved Cannot Reproduce nasf Maloo Tue, 2 Sep 2014 16:39:27 +0000 Thu, 19 Feb 2015 15:45:22 +0000 Sat, 27 Sep 2014 02:41:50 +0000 Lustre 2.7.0 0 5 <p>Fan Yong,<br/> Can you comment on this one please?<br/> Thank you!</p> <p>The zfs-based backend seems some slow. I have changed the test scripts (in the patch <a href="http://review.whamcloud.com/#/c/10987/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/10987/</a> set 16) to wait more long time for the LFSCK status changing. Let's see what will happen after such patch applied.</p> <p>Nathaniel,<br/> Could you run the test with this patch applied to see if it corrects the issue?<br/> Thank you!</p> <p>I cannot reproduce with 10987 applied and I don't see any failures on builds that include the patch (10987).</p> <p>Close it since it is cannot be reproduced after the patch applied.</p> <p>There are a large number of these failures being generated by the <a href="https://jira.whamcloud.com/browse/LU-3534" title="async update cross-MDTs" class="issue-link" data-issue-key="LU-3534"><del>LU-3534</del></a> patch series, in particular:</p> <p><a href="http://review.whamcloud.com/10794" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10794</a><br/> <a href="http://review.whamcloud.com/10939" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10939</a></p> <p>but I'm tracking those under <a href="https://jira.whamcloud.com/browse/LU-3534" title="async update cross-MDTs" class="issue-link" data-issue-key="LU-3534"><del>LU-3534</del></a> instead of this ticket, which may not be related.</p> <p>The sanity-lfsck failures for DNE are not the same. The original test_13 failed because the low layer iteration was too slow to complete the LFSCK in time. The general behavior is that the final status was "scanning-phase2", but not the expected "completed".</p> <p>The failures for the DNE patches were that the test scripts cannot find the specified lproc interface "error: get_param: mdd/lustre-MDT0000/lfsck_layout: Found no match". I am still not sure what caused such failure, but it should not be related with the iteration performance.</p> Related LU-3534 Development Rank 1|hzwv3z: Rank (Obsolete) 15540 Severity