Following up on this for NFS as I made a sneaky bug report hard to notice, this might be worth having a look: Dominique Martinet wrote on Fri, Jan 25, 2019: > [...] There is a small, few seconds window > where I can reproduce a similar issue on nfs: > $ echo foo > bar; stat -c %b bar; sleep 3; stat -c %b bar > 0 > 8 > with a 4.14.87 knfsd and 4.19.15-300.fc29 client, nfs 4.2, both x86_64, > no export option or explicit client option. In other words, the file's i_blocks isn't updated for a short while on nfs v4 which might lead to data loss (see previous email for example e.g. tar), just create a file and immediately stat to notice. nfs v3 doesn't exhibit the problem. I also wasn't able to reproduce on the 4.14.87 machine as a and nfs v4 client so it's likely a semi-recent regression, I could probably bissect it if really required but I'm sure someone here has some dedicated hardware for this better than my laptop :) Feel free to ask if you cannot reproduce and I'll try updating to master on both client and server just in case. Thanks, -- Dominique
