[lkml]   [2012]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH RFC v3] vfs: make fstatat retry once on ESTALE errors from getattr call
    On Fri, 20 Apr 2012 15:37:26 -0500
    Malahal Naineni <> wrote:

    > Steve Dickson [] wrote:
    > > > 2) if we assume that it is fairly representative of one, how can we
    > > > achieve retrying indefinitely with NFS, or at least some large finite
    > > > amount?
    > > The amount of looping would be peer speculation. If the problem can
    > > not be handled by one simple retry I would say we simply pass the
    > > error up to the app... Its an application issue...
    > As someone said, ESTALE is an incorrect errno for a path based call.
    > How about turning ESTALE into ENOENT after a retry or few retries?

    It's not really the same thing. One could envision an application
    that's repeatedly renaming a new file on top of another one. The file
    is never missing from the namespace of the server, but you could still
    end up getting an ESTALE.

    That would break other atomicity guarantees in an even worse way, IMO...

    Jeff Layton <>

     \ /
      Last update: 2012-04-20 23:15    [W:0.020 / U:18.920 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site