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-6785 Lustre <p>This issue was created by maloo for sarah_lw &lt;wei3.liu@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/a260a392-1237-11e5-bd2d-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/a260a392-1237-11e5-bd2d-5254006e85c2</a>.</p> <p>The sub-test test_56w failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>/usr/bin/lfs migrate -i 0 /mnt/lustre/d56w.sanityw/migr_1_ost failed </pre> </div></div> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>yes: standard output: Broken pipe yes: write error /usr/bin/lfs_migrate -y -c 6 /mnt/lustre/d56w.sanityw/file1 /mnt/lustre/d56w.sanityw/file1: /usr/bin/lfs: /mnt/lustre/d56w.sanityw/file1: cannot swap layouts: Device or resource busy cannot put lease: No locks available (37) error: migrate: migrate stripe file '/mnt/lustre/d56w.sanityw/file1' failed falling back to rsync-based migration done </pre> </div></div> server: 2.7.0<br/> client: lustre-master build # 3071 EL7 LU-6785

Interop 2.7.0<->master sanity test_56w: cannot swap layouts: Device or resource busy

Bug Critical Resolved Fixed Henri Doreau Maloo Wed, 1 Jul 2015 18:23:48 +0000 Wed, 28 Oct 2020 21:41:19 +0000 Thu, 10 Sep 2015 15:07:01 +0000 Lustre 2.8.0 Lustre 2.8.0 0 7 <p>It seems that this interop regression was added from <a href="http://review.whamcloud.com/10013" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10013</a> "<a href="https://jira.whamcloud.com/browse/LU-4840" title=" Deadlock when truncating file during lfs migrate" class="issue-link" data-issue-key="LU-4840"><del>LU-4840</del></a> lfs: Use file lease to implement migration" which landed back on 2015-05-28. This landed after the 2.5.54 tag was made (2015-05-17) and first appeared in the 2.7.55 tag (2015-06-10) .</p> <p>I'd guess that the new client is always trying to use the file lease lock, but that doesn't exist in 2.7.0 and earlier (interop failures are seen with 2.5.x also). Is there some mechanism by which the client can determine if the MDS has the file lease capability, and fall back to the previous group lock mechanism?</p> <p>The file_lease_supported variable in lfs was supposed to address this. It is set automatically on failed attempts to get a file lease and it determines whether to fallback on group lock or not. Obviously there's something fishy, I can reproduce easily. I'm having a look.</p> <p>Henri Doreau (henri.doreau@cea.fr) uploaded a new patch: <a href="http://review.whamcloud.com/16238" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16238</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6785" title="Interop 2.7.0&lt;-&gt;master sanity test_56w: cannot swap layouts: Device or resource busy" class="issue-link" data-issue-key="LU-6785"><del>LU-6785</del></a> utils: compatibility fix for lfs migrate<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 0e4820031647405d939ccf43be8bc76426310b9f</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/16238/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16238/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6785" title="Interop 2.7.0&lt;-&gt;master sanity test_56w: cannot swap layouts: Device or resource busy" class="issue-link" data-issue-key="LU-6785"><del>LU-6785</del></a> utils: compatibility fix for lfs migrate<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: a99e42c9fa47677cd2468abfa9378d776cc40803</p> <p>Landed for 2.8.0</p> Related LU-4840 LU-6475 LU-14084 Development Rank 1|hzxgzj: Rank (Obsolete) 9223372036854775807 Severity