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-5748 Lustre <p>This issue was created by maloo for Doug Oucharek &lt;doug@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/ed4f6082-53f1-11e4-a9db-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/ed4f6082-53f1-11e4-a9db-5254006e85c2</a>.</p> <p>The sub-test test_9b failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>(5) unexpected status </pre> </div></div> <p>Please provide additional information about the failure here.</p> <p>Info required for matching: sanity-lfsck 9b</p> LU-5748

sanity-lfsck test_9b: unexpected status

Bug Major Resolved Duplicate nasf Maloo Wed, 15 Oct 2014 23:31:47 +0000 Fri, 20 Feb 2015 15:00:35 +0000 Tue, 21 Oct 2014 02:10:47 +0000 Lustre 2.7.0 0 2 <p>According to the log on MDT, the LFSCK assistant thread triggered the error stub (#define OBD_FAIL_LFSCK_NO_DOUBLESCAN 0x160c) as expected, and began to handle the exiting, but the test timeout before the assistant thread exit.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">00100000:10000000:0.0:1413319551.677715:0:28817:0:(lfsck_engine.c:1568:lfsck_assistant_engine()) lustre-MDT0000-osd: LFSCK assistant phase2 scan start 00100000:02000000:0.0:1413319551.677721:0:28817:0:(libcfs_fail.h:96:cfs_fail_check_set()) *** cfs_fail_loc=160c, val=0*** 00100000:10000000:0.0:1413319551.679212:0:28817:0:(lfsck_engine.c:1662:lfsck_assistant_engine()) lustre-MDT0000-osd: LFSCK assistant unknown status: rc = 0 00080000:00080000:0.0:1413319551.679229:0:28817:0:(osd_handler.c:541:osd_sync()) syncing OSD osd-zfs ... </pre> </div></div> <p>So there are two possible cases:<br/> 1) The test_9b should wait more long time for the LFSCK to commit async updating.<br/> 2) Something wrong inside the dt_sync() and caused the LFSCK assistant thread could not exit in time.</p> <p>Since there are no sync related failures in the logs, and there are some known performance issues for zfs-based backend, I more suspect that we should increase the lfsck tests timeout. There is another ticket for that <a href="https://jira.whamcloud.com/browse/LU-5301" title="Test failure sanity-lfsck test_17: (3) unexpected status" class="issue-link" data-issue-key="LU-5301"><del>LU-5301</del></a>.</p> <p>It is another instance of <a href="https://jira.whamcloud.com/browse/LU-5301" title="Test failure sanity-lfsck test_17: (3) unexpected status" class="issue-link" data-issue-key="LU-5301"><del>LU-5301</del></a>.</p> Development Rank 1|hzwynr: Rank (Obsolete) 16141 Severity