Good day, It seems that fsync(2) may data after returning EIO once[1]. This behaviour seems to cause problems with databases such as PostgreSQL and goes contrary to the man page's description, which says that "fsync() and fdatasync() should be used by programs that require a file to be in a known state, for example, in building a simple transaction facility."
Are there any plans to change fsync(2) to allow for retries and/or persistent error reporting? [1] https://wiki.postgresql.org/wiki/Fsync_Errors Thank you for your time. Regards, Maximilian Lorlacks
