És erre ilyen válaszok jöttek, egy részük @nginx-es e-mail címel:
"(Also, trying to do fsync() might not be the best idea even in threads. A reliable server might be a better option.)"
"I understand why one may need consistency, but doing so with fsyncing is non-sense."
"So it’s not a great way to ensure consistency.
But there are cheaper ways to achieve the same consistency and reliability characteristics:
If you are using Linux then your reads and write swill occur through the page cache - so the actual disk itself really doesn’t matter (whilst your host is up).
If you want to protect against loss of physical disk then use RAID.
If you want to protect against a random power failure then use drives with battery backed caches, so writes will get persisted when a server restarts after a power failure
If you want to protect against a crazy person hitting your server with an axe then write to two servers ...
But the bottom line is separation of concerns. Nginx should not use fsync because it isn’t nginx's business."
"The question here is - why you want the file to be on disk, and not just in a buffer? Because you expect the server to die in a few seconds without flushing the file to disk? How probable it is, compared to the probability of the disk to die? A more reliable server can make this probability negligible, hence the suggestion."
Ezek elvileg komoly, értelmes emberek. Elbizonytalanodtam. Csak én megyek szembe az autópályán?