Larry Schwimmer <[EMAIL PROTECTED]> writes:
> What does fsync(2) do for files in AFS (afs33a)? Does it
> return after the file has been written to the cache (but not
> necessarily server) or after the file has been written to the server?
It returns after the data is on stable storage at the server, unless
the server is unavailable or the volume has been removed or is
otherwise offline (not merely busy), in which case it will return an
error code. If fsync fails, you should be able to retry it at a
later time. Note that this didn't always work correctly, though I'm
not certain in which version of AFS the fix first appeared --
certainly not before 3.3.