News for hackers. Stuff that matters.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by rodgerd on Sunday July 21, 2019 @03:55PM (#20493307)
So kernel panic on disk full errors? Because that's one of the scenarios causing data loss here - fsync throwing away data on a full disk and lying about having committed it.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by masklinn on Monday July 22, 2019 @02:13AM (#20495691)
In that thread, Craig Ringer and Thomas Munro notes most systems & FS won't report ENOSPC on fsync(), they'll do that on write():

> ENOSPC doesn't seem to be a concern during normal operation of major file systems (ext3, ext4, btrfs, xfs) because they reserve space before returning from write(). But if a buffered write does manage to fail due to ENOSPC we'll definitely see the same problems. This makes ENOSPC on NFS a potentially data corrupting condition since NFS doesn't preallocate space before returning from write().

Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by limitthis on Sunday July 21, 2019 @07:09PM (#20494269)
no, the fs doesn’t overcommit storage like the memory system does.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by rodgerd on Monday July 22, 2019 @06:19AM (#20496677)
I don't think you understand the problem.