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-7860 Lustre <p>This is an OSS node error encountered while running a 56 node/260 process IOR. </p> <p>This is not a server-client combo that is likely to see production, but I'd guess any ASSERT triggered would be of interest.</p> <p>The IOR jobs were failing on one of the 56 clients with ENOTDIR on attempting to open the data file.</p> servers: (zfs) v2_8_0_0_RC2--PRISTINE-3.10.0-327.0.0.1chaos.ch6.x86_64 <br/> clients: 2.5-5chaos-CHANGED-3.10.0-327.10.1.1chaos.ch6.x86_64 LU-7860

LustreError: 19445:0:(ldlm_lock.c:2273:ldlm_lock_cancel()) ASSERTION( !(((( lock))->l_flags & (1ULL << 53)) != 0) ) failed

Bug Minor Resolved Fixed Zhenyu Xu Ruth Klundt Wed, 9 Mar 2016 20:01:42 +0000 Thu, 14 Jun 2018 21:41:20 +0000 Tue, 9 May 2017 19:34:04 +0000 Lustre 2.8.0 Lustre 2.9.0 0 8 <p>Hi Ruth,<br/> Do you intend this to be a severity 1 (meaning site is down)?<br/> Thanks.<br/> Joe</p> <p>Ruth</p> <p>You have flagged this ticket as severity 1 - meaning a production filesystem out of service. Looking at the details supplied it looks like this relates to testing you are doing on the community 2.8 release so I am wondering if your intention was to select the lowest severity (4)?</p> <p>Peter</p> <p>oops, sorry I meant lowest severity, so apparently I meant 5, 'not sever at all' </p> <p>ok - no problem <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Liang, apparently this is assertion that you have introduced and apparently it's incorrect and the previous handling for it was correct.<br/> Would be greet f you can take another look.</p> <p>Ruth, can you please upload a log from the crashed server if you have it? with a backtrace and all.</p> <p>Hi Liang,</p> <p>Can you please have a look at the change?</p> <p>Thanks.<br/> Joe</p> <p>The console log got very little info and no backtrace. syslog got nothing, I may have time to try to reproduce this week.</p> <p>&lt;ConMan&gt; Console <span class="error">&#91;cs48&#93;</span> log at 2016-03-04 19:00:00 MST.<br/> 2016-03-04 19:12:26 <span class="error">&#91;28608.194920&#93;</span> Lustre: scratch4-OST001c: haven't heard from client 15c8341e-dd93-ee2b-fcaa-2c59e0dea086 (at 172.17.70.108@o2ib) in 227 seconds. I think it's dead, and I am evicting it. exp ffff8800b63fc800, cur 1457143946 expire 1457143796 last 1457143719<br/> 2016-03-04 19:12:26 <span class="error">&#91;28608.217293&#93;</span> Lustre: Skipped 3 previous similar messages<br/> 2016-03-04 19:35:46 <span class="error">&#91;30009.200717&#93;</span> LustreError: 19445:0:(ldlm_lock.c:2273:ldlm_lock_cancel()) ASSERTION( !(((( lock))-&gt;l_flags &amp; (1ULL &lt;&lt; 53)) != 0) ) failed:<br/> 2016-03-04 19:35:46 <span class="error">&#91;30009.212987&#93;</span> LustreError: 19445:0:(ldlm_lock.c:2273:ldlm_lock_cancel()) LBUG<br/> 2016-03-04 19:35:46 <span class="error">&#91;30009.219959&#93;</span> Pid: 19445, comm: ldlm_cn03_003</p> <p>Bobi Jam (bobijam@hotmail.com) uploaded a new patch: <a href="http://review.whamcloud.com/20509" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/20509</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7860" title="LustreError: 19445:0:(ldlm_lock.c:2273:ldlm_lock_cancel()) ASSERTION( !(((( lock))-&gt;l_flags &amp; (1ULL &lt;&lt; 53)) != 0) ) failed" class="issue-link" data-issue-key="LU-7860"><del>LU-7860</del></a> ldlm: revert part of commit 79e81d22<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 8fc1eb987b20d3323b91fc38fe3b1ef17f3b071e</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/20509/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/20509/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7860" title="LustreError: 19445:0:(ldlm_lock.c:2273:ldlm_lock_cancel()) ASSERTION( !(((( lock))-&gt;l_flags &amp; (1ULL &lt;&lt; 53)) != 0) ) failed" class="issue-link" data-issue-key="LU-7860"><del>LU-7860</del></a> ldlm: revert part of commit 657bbc49<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 62a859fade43e23636170d054a4385d5b669774c</p> <p>Patch has landed to master for 2.9.0</p> <p>LLNL hit this on a 2.8 server today. Please consider landing the fix to b2_8_fe. Thanks</p> <p>Ned</p> <p>As far as the community releases is concerned, this is fixed in 2.9. If you want a separate support ticket to track fixing on an FE release then we can link to this one.</p> <p>Peter</p> <p>PS/ THere is already a 2.8 FE port of this fix, it just needs to be integrated</p> <p>Thanks Peter. I don't think we need a separate ticket. Let's just make sure that patch gets in the next 2.8 FE tag.</p> <p>Sure. It was already flagged for inclusion.</p> Related LU-6416 Development End date Mon, 6 Jun 2016 20:01:42 +0000 Rank 1|hzy40n: Rank (Obsolete) 9223372036854775807 Severity Start date Wed, 9 Mar 2016 20:01:42 +0000