News for hackers. Stuff that matters.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by jcranmer on Sunday July 21, 2019 @02:14PM (#20492764)
> If the kernel can't flush dirty write buffers, maybe it's time to send up a flag and panic in the kernel itself?

Being unable to write to a disk is a recoverable scenario, especially in some conditions. The most common cause of disk write failures is "someone yanked the flash drive out of the computer," and the recovery is "pop up a dialog telling the user to put it back in."

Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by carbocation on Sunday July 21, 2019 @02:31PM (#20492872)
Another situation: a GCSFuse volume dealing with temporary networking errors.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by masklinn on Monday July 22, 2019 @02:08AM (#20495674)
Or NFS being NFS.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by tinus_hn on Monday July 22, 2019 @05:19AM (#20496412)
That would be a great improvement over the ‘tell the user he shouldn’t have done that’ we have now!
Re:Fsyncgate: Errors on fsync are unrecoverable (2018) by londons_explore on Sunday July 21, 2019 @06:51PM (#20494177)
I think there is a case for never throwing away dirty pages.

Ie. either the write eventually succeeds, or all other writes will block or fail until it does.