[LU-14949] gap in rename atomicity: possible to get ENOENT when renaming over an existing file Created: 17/Aug/21  Updated: 17/Sep/21  Resolved: 31/Aug/21

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.15.0

Type: Bug Priority: Minor
Reporter: Patrick Farrell Assignee: Patrick Farrell
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

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.

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.

 Comments   
Comment by Patrick Farrell [ 17/Aug/21 ]

See https://review.whamcloud.com/#/c/44675/

Comment by Gerrit Updater [ 31/Aug/21 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/44675/
Subject: LU-14949 llite: Always do lookup on ENOENT in open
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 72c1f7095203cc1badadf581c66f9546476438ab

Comment by Peter Jones [ 31/Aug/21 ]

Landed for 2.15

Generated at Sat Feb 10 03:14:09 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.