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-14949 Lustre <p>When doing a rename/mv of a file over the top of an existing file, there is a race with an open of that existing while where that open can get ENOENT.</p> <p>This race is due to a combination of OPEN_BY_FID and our dentry caching behavior and can be resolved by a change to the handling of opens.</p> LU-14949

gap in rename atomicity: possible to get ENOENT when renaming over an existing file

Bug Minor Resolved Fixed Patrick Farrell Patrick Farrell Tue, 17 Aug 2021 14:11:04 +0000 Fri, 17 Sep 2021 23:47:44 +0000 Tue, 31 Aug 2021 11:56:09 +0000 Lustre 2.15.0 0 4 <p>See <a href="https://review.whamcloud.com/#/c/44675/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/44675/</a></p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/44675/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/44675/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14949" title="gap in rename atomicity: possible to get ENOENT when renaming over an existing file" class="issue-link" data-issue-key="LU-14949"><del>LU-14949</del></a> llite: Always do lookup on ENOENT in open<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 72c1f7095203cc1badadf581c66f9546476438ab</p> <p>Landed for 2.15</p> Related Development Rank 1|i02207: Rank (Obsolete) 9223372036854775807 Severity