Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-14949

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

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.15.0
    • None
    • None
    • 3
    • 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.

      Attachments

        Activity

          [LU-14949] gap in rename atomicity: possible to get ENOENT when renaming over an existing file
          pjones Peter Jones added a comment -

          Landed for 2.15

          pjones Peter Jones added a comment - Landed for 2.15

          "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

          gerrit Gerrit Updater added a comment - "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
          paf0186 Patrick Farrell added a comment - - edited See https://review.whamcloud.com/#/c/44675/

          People

            paf0186 Patrick Farrell
            paf0186 Patrick Farrell
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: