Comment 165 for bug 317781

@helios

I fail to see the fact that this would ever be a KDE bug. fsync only *helps*, it will never ever make sure that things will be solved permanently for good. The reason that a rename() is used with a temp file that *nothing* can get 100% durability (even using fsync). App developers want atomicity (with rename), because atomicity, they can get with a good filesystem design and implementation. 100% durability is impossible, power syncs during a fsync will also result in halfly written files, it will still suck that the rename() has been done at that point.

Hence, as it is impossible to solve the problem of durability with fsync and because fsync is slow, it should not even be used IMHO.