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-8279 Lustre <p>This issue was created by maloo for nasf &lt;fan.yong@intel.com&gt;</p> <p>Please provide additional information about the failure here.</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/e3ebda8e-3257-11e6-80b9-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/e3ebda8e-3257-11e6-80b9-5254006e85c2</a>.</p> <p>There is inode reference leak</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>CMD: trevis-15vm1.trevis.hpdd.intel.com,trevis-15vm2,trevis-15vm3,trevis-15vm4,trevis-15vm8 dmesg Kernel error detected: [11602.132484] VFS: Busy inodes after unmount of dm-1. Self-destruct in 5 seconds. Have a nice day... [11616.134774] VFS: Busy inodes after unmount of dm-3. Self-destruct in 5 seconds. Have a nice day... [11610.008080] VFS: Busy inodes after unmount of dm-2. Self-destruct in 5 seconds. Have a nice day... sanity-scrub test_4b: @@@@@@ FAIL: Error in dmesg detected </pre> </div></div> LU-8279

sanity-scrub test_4b: @@@@@@ FAIL: Error in dmesg detected

Bug Blocker Resolved Fixed nasf Maloo Wed, 15 Jun 2016 02:16:49 +0000 Thu, 4 May 2017 20:20:02 +0000 Fri, 17 Jun 2016 01:05:52 +0000 Lustre 2.9.0 Lustre 2.9.0 0 8 <p>Fan Yong (fan.yong@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/20792" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/20792</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8279" title="sanity-scrub test_4b: @@@@@@ FAIL: Error in dmesg detected" class="issue-link" data-issue-key="LU-8279"><del>LU-8279</del></a> scrub: fix inode reference leak<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: c47ef8662201217076bac09dcf50c867e7752545</p> <p>Is there any explanation why this started failing? Is it due to some patch being landed that had a bug? If yes, did that patch also fail testing, but this problem was missed? </p> <p>It looks like this is related to the landing of one of the patches:</p> <ul class="alternate" type="square"> <li><a href="http://review.whamcloud.com/18175" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/18175</a> "<a href="https://jira.whamcloud.com/browse/LU-7302" title="sanity-lfsck test_23b hangs on START_NAMESPACE" class="issue-link" data-issue-key="LU-7302"><del>LU-7302</del></a> scrub: join the running OI scrub properly"</li> <li><a href="http://review.whamcloud.com/16951" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16951</a> "<a href="https://jira.whamcloud.com/browse/LU-6861" title="sanity-scrub test 4a and 4b fail: Auto trigger full scrub unexpectedly" class="issue-link" data-issue-key="LU-6861"><del>LU-6861</del></a> scrub: only trigger full OI scrub when necessary"</li> </ul> <p>It would be worthwhile to investigate if this problem hit on either of those patches before landing?</p> <p>It is introduced by the patch <a href="http://review.whamcloud.com/#/c/16951/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/16951/</a>. But related failure under such patch has never been triggered before.</p> <p>That may be related with the system schedule order: if the OI scrub run faster, and it could has already repaired the invalid OI mapping for the remote directory object before related RPC handler to call osd_fid_lookup() to locate such remote directory object.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/20792/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/20792/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8279" title="sanity-scrub test_4b: @@@@@@ FAIL: Error in dmesg detected" class="issue-link" data-issue-key="LU-8279"><del>LU-8279</del></a> scrub: fix inode reference leak<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 1738f00d4a4cee01a2c39a6313acabdcb5775269</p> <p>The patch has been landed to master.</p> Related LU-9433 LU-8278 Development Rank 1|hzyeon: Rank (Obsolete) 9223372036854775807 Severity