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-10443 Lustre <p>This issue was created by maloo for Saurabh Tandan &lt;saurabh.tandan@intel.com&gt;</p> <p>This issue relates to the following test suite run: </p> <p><a href="https://testing.hpdd.intel.com/test_sets/515b6450-ebfb-11e7-8c23-52540065bddc" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/515b6450-ebfb-11e7-8c23-52540065bddc</a></p> <p>This issue occurred while performing rolling upgrade/downgrade testing for tag 2.10.56_62.<br/> Both the servers and clients are 2.10.56_62 lustre versions. Hence both must support Lockahead.</p> <p>test logs:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>== sanity test 255c: suite of ladvise lockahead tests ================================================ 07:51:57 (1514361117) Starting test test10 at 1514361118 Finishing test test10 at 1514361118 Starting test test11 at 1514361118 Finishing test test11 at 1514361118 Starting test test12 at 1514361118 Finishing test test12 at 1514361119 Starting test test13 at 1514361119 Finishing test test13 at 1514361119 sanity test_255c: @@@@@@ FAIL: Ladvise test 13, bad lock count, returned 100, actual 0 </pre> </div></div> <p>Might be related to <a href="https://jira.whamcloud.com/browse/LU-10136" title="sanity test_255c: Ladvise test11 failed, 255" class="issue-link" data-issue-key="LU-10136"><del>LU-10136</del></a> and <a href="https://jira.whamcloud.com/browse/LU-10104" title="sanity test_255c: Ladvise test 15, bad lock count, returned 5000, actual 4538" class="issue-link" data-issue-key="LU-10104"><del>LU-10104</del></a></p> Rolling Upgrade/Downgrade<br/> Servers/Clients = 2.10.56_62 lustre version<br/> ldiskfs LU-10443

sanity - test_255c: Ladvise test 13, bad lock count, returned 100, actual 0

Bug Minor Resolved Fixed Patrick Farrell Maloo Thu, 28 Dec 2017 18:35:22 +0000 Thu, 2 Mar 2023 00:26:04 +0000 Thu, 22 Feb 2018 13:26:08 +0000 Lustre 2.11.0 Lustre 2.11.0 0 5 <p>Patrick</p> <p>Could you please advise on this one?</p> <p>Peter</p> <p>Sure, will take a look.</p> <p>Steps followed for Rolling Upgrade testing:<br/> 1. Setup Lustre with clients and servers both having 2.10.2 GA version.<br/> 2. Upgrade OSS to 2.10.56_62 , Ran Sanity.sh<br/> 3. Upgrade MDS to 2.10.56_62 , Ran Sanity.sh<br/> 4. Upgrade Clients to 2.10.56_62, Ran Sanity.sh and hit this issue.</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=paf" class="user-hover" rel="paf">paf</a> when do you expect to have a chance to get to this?</p> <p>Tomorrow or early next week, sorry, I didn't realize this was urgent (passed on to me from the LWG today). I can try to reproduce the procedure described.</p> <p>So to be clear, sanity was run with everything at 2.10.2, OSSes were unmounted and upgraded - I assume the file system remains <b>up</b> for this, this is a failover type scenario? Then sanity run again. Then the same for the MDS, followed by sanity.</p> <p>And then finally, clients were all unmounted and upgraded, then remounted, followed by sanity, which had this failure?</p> <p>I can replicate most of this, but I strongly suspect I won't hit this issue. Lockahead creates no on disk state, only LDLM state which should be destroyed well, A) when the file is deleted, and B) when clients are unmounted and remounted. I think it's way more likely we hit some other rare issue with the test rather than this being upgrade related.</p> <p>First I'll dig through the logs and see if I can find anything.</p> <p>... woah. Well, this test should never pass and neither should any of the others, really. We unlink the file and check the lock count after that. I guess we're just consistently winning the race.</p> <p>I'll get a patch generated. This is a bug in the test, if that affects urgency.</p> <p>Patrick Farrell (paf@cray.com) uploaded a new patch: <a href="https://review.whamcloud.com/31254" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31254</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10443" title="sanity - test_255c: Ladvise test 13, bad lock count, returned 100, actual 0" class="issue-link" data-issue-key="LU-10443"><del>LU-10443</del></a> test: Handle file lifecycle correctly<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 286e0f7839267b8bf4119ce084427ffeb20455f6</p> <p>This bug is not specific to interop. Just a question of timing. Patch should resolve.</p> <p>Thanks Patrick! Good to know that this is not something that would affect those using the feature for real. <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/31254/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31254/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10443" title="sanity - test_255c: Ladvise test 13, bad lock count, returned 100, actual 0" class="issue-link" data-issue-key="LU-10443"><del>LU-10443</del></a> test: Handle file lifecycle correctly<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: e528677e1630093362394ae36d725c321d0da4f2</p> <p>Landed for 2.11</p> Related LU-10104 LU-10136 LU-16608 Development Rank 1|hzzq87: Rank (Obsolete) 9223372036854775807 Severity