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-7706 Lustre <p>conf sanity 83 may fail with message:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>conf-sanity test_83: @@@@@@ FAIL: VFS: Busy inodes after unmount of vdb. Self-destruct in 5 seconds. Have a nice day... </pre> </div></div> <p>Dmesg clearing is needed in conf-sanity 83 because previous tests<br/> (for example conf-sanity_62) may also be the results of message "VFS: Busy inodes after unmount of ...".</p> LU-7706

add dmesg -c to conf-sanity_83

Bug Minor Resolved Won't Fix WC Triage Sergey Cheremencev patch Mon, 25 Jan 2016 15:39:21 +0000 Tue, 5 Apr 2016 15:13:19 +0000 Tue, 5 Apr 2016 15:13:19 +0000 0 3 <p>Sergey Cheremencev (sergey_cheremencev@xyratex.com) uploaded a new patch: <a href="http://review.whamcloud.com/18122" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/18122</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7706" title="add dmesg -c to conf-sanity_83" class="issue-link" data-issue-key="LU-7706"><del>LU-7706</del></a> tests: add dmesg -c to conf-sanity_83<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: dca4bf26e5177ece36d6d528106f1b033424c6d3</p> <p>It seems bad that any test causes the "VFS: Buay inodes ..." message to be hit. It would be better to find and fix that problem rather than working around this to allow the test to pass. </p> <p>The problem is fixed right now(in seagate) - it needs a kernel fix. But I didn't send it upstream yet.<br/> If you also face this problem("busy inodes" after conf-sanity 62) I can send it faster or make a kernel patch for lustre.</p> <p>conf-sanity_83 checks that there is no "busy inodes" messages caused by ENOSPACE on OST.<br/> Why Does it need to fail when message is caused by another issue(theoretically not lustre related issue) ?<br/> Even if the "busy inodes" after conf-sanity 62 will disappear there is no guarantee that another test will not cause the same message. </p> <p>Earlier in <a href="https://jira.hpdd.intel.com/browse/LU-7227" class="external-link" target="_blank" rel="nofollow noopener">https://jira.hpdd.intel.com/browse/LU-7227</a> I suggested to fail tests that lead to kernel errors like "VFS: Busy inodes ..."<br/> New lustre code or fix may introduce "missed iput" and "VFS: busy inodes" as result. And it is better to find this error in testing if possible.</p> <blockquote> <p>New lustre code or fix may introduce "missed iput" and "VFS: busy inodes" as result. And it is better to find this error in testing if possible.</p></blockquote> <p>Right, so we should detect this failure even if it happened in a previous test, so erasing the previous messages isn't helpful. The fix in <a href="https://jira.whamcloud.com/browse/LU-7227" title="Add a check to t-f that dmesg doesn&#39;t have critical messages" class="issue-link" data-issue-key="LU-7227"><del>LU-7227</del></a> seems a lot better, since it catches the failure right away. I don't recall seeing that bug/patch, but I'd think it better to abandon this patch and ticket in favor of that one.</p> <p>Landed patch from <a href="https://jira.whamcloud.com/browse/LU-7227" title="Add a check to t-f that dmesg doesn&#39;t have critical messages" class="issue-link" data-issue-key="LU-7227"><del>LU-7227</del></a> instead. </p> Related LU-7227 Development Rank 1|hzxz9r: Rank (Obsolete) 9223372036854775807 Severity