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-6236 Lustre <p>This ticket reports the same issue than <a href="https://jira.whamcloud.com/browse/LU-5522" title="ofd_prolong_extent_locks()) ASSERTION( lock-&gt;l_flags &amp; 0x0000000000000020ULL ) failed" class="issue-link" data-issue-key="LU-5522"><del>LU-5522</del></a>.</p> <p>It occured at customer site on Lustre version 2.5.3 with a few additional patches.</p> <p>According to the Bull support team, the issue could be a side effect of the fix <a href="http://review.whamcloud.com/#/c/10492/" class="external-link" target="_blank" rel="nofollow noopener">#10492</a> for <a href="https://jira.whamcloud.com/browse/LU-2827" title="mdt_intent_fixup_resent() cannot find the proper lock in hash" class="issue-link" data-issue-key="LU-2827"><del>LU-2827</del></a>, which is one of the addtional patch we apply on top of 2.5.3.</p> <p>I have posted the patch <a href="http://review.whamcloud.com/#/c/13744/" class="external-link" target="_blank" rel="nofollow noopener">#13744</a> in b2_5, which is the backport of the master patch <a href="http://review.whamcloud.com/#/c/11634/" class="external-link" target="_blank" rel="nofollow noopener">#11634</a> that fixes <a href="https://jira.whamcloud.com/browse/LU-5522" title="ofd_prolong_extent_locks()) ASSERTION( lock-&gt;l_flags &amp; 0x0000000000000020ULL ) failed" class="issue-link" data-issue-key="LU-5522"><del>LU-5522</del></a>.</p> <p>If the support assumption is confirmed, since <a href="https://jira.whamcloud.com/browse/LU-2827" title="mdt_intent_fixup_resent() cannot find the proper lock in hash" class="issue-link" data-issue-key="LU-2827"><del>LU-2827</del></a> is integrated into the future 2.5.4 maintenance release, it will be required to have this fix in 2.5.4 also.</p> LU-6236

ost_prolong_locks()) ASSERTION( lock->l_flags & 0x0000000000000020ULL ) failed

Bug Minor Resolved Duplicate Bruno Faccini Gregoire Pichon Thu, 12 Feb 2015 08:52:10 +0000 Wed, 13 Oct 2021 03:05:07 +0000 Wed, 13 Oct 2021 03:05:07 +0000 Lustre 2.5.3 0 6 <p>Bruno,<br/> Could you have a look at this one and comment?<br/> Thank you!</p> <p>Lustre 2.5.3 + <a href="https://jira.whamcloud.com/browse/LU-2827" title="mdt_intent_fixup_resent() cannot find the proper lock in hash" class="issue-link" data-issue-key="LU-2827"><del>LU-2827</del></a> has been installed on 01/21. First occurrence of this LBUG happened on 01/23. Then we had 6 LBUG in a row (2 hours window) on 02/05, and one on another filesystem on monday. We have 5000+ Lustre clients. I think this fix should be considered for inclusion in 2.5.4.</p> <p>If you need further information, please let me know.</p> <p>Hello Bruno,<br/> There is no evidence that this problem is a regression from patch <a href="https://jira.whamcloud.com/browse/LU-2827" title="mdt_intent_fixup_resent() cannot find the proper lock in hash" class="issue-link" data-issue-key="LU-2827"><del>LU-2827</del></a>, but I agree with you that Gregoire's b2_5 version of patch for <a href="https://jira.whamcloud.com/browse/LU-5522" title="ofd_prolong_extent_locks()) ASSERTION( lock-&gt;l_flags &amp; 0x0000000000000020ULL ) failed" class="issue-link" data-issue-key="LU-5522"><del>LU-5522</del></a> should be included in 2.5.4. </p> Related LU-5522 Development End date Thu, 23 Apr 2015 08:52:10 +0000 Rank 1|hzx68f: Rank (Obsolete) 17472 Severity Start date Thu, 12 Feb 2015 08:52:10 +0000