On: NFS > FUSE: Why We Built Our Own NFS Server in Rus...

[LeoPanthera]

NFS4 is a huge ugly bloated mess of a protocol, and they keep adding more stuff to it.

NFS3 is small (I wouldn't say "elegant" but by comparison...), works, and doesn't have anything wrong with it.

[chungy → LeoPanthera]

NFSv4 has sane, good locking out of the box. Implementing lockd on an NFSv3 server is a big world of hurt.

[hedora → chungy]

Is there some way to configure NFSv4 not to silently corrupt data or surface transient network errors to userspace?

(Correct NFSv3 implementations block forever, which is the best of three bad alternatives.)

https://access.redhat.com/solutions/1179643

[chungy → hedora]

NFSv4 should never do that, and I've never seen it happen.

[notacoward → chungy]

Then again, if you're using file locking on a distributed filesystem at non-trivial scale you're in for a big world of hurt anyway. Source: I was a developer and maintainer of exactly such a beast for over a decade.