2 ms·
The lack of posix semantics when unlinking on NFS rears its ugly head in many more places. For example the common atomic write pattern that allows readers to ke
by the8472 7y ago
The lack of posix semantics when unlinking on NFS rears its ugly head in many more places. For example the common atomic write pattern that allows readers to keep reading a stale copy doesn't work anymore (you get ESTALE on IO or SIGBUS if it's mmaped) which means anything involving a frequently replaced file will require more workarounds than on any other filesystem.
- jabl 7y agoIsn't that what "silly rename" (on nfsv3, v4 doesn't need it?) is supposed to fix? The problem the article mentions is overwritin a binary instead of renaming.
- the8472 7y agoThe article is about the atomic write pattern: create tempfile, move tempfile over original which effectively is an unlink of the original. And yes, this should be solved, but some NFS servers don't support it, e.g. AWS's EFS.