Fsyncers and curveballs (the Firefox 3 fsync() problem)

I can't blame firefox.

It seems to me that fsync is the problem.  No user level program should have access to any
kind of system call that can cause this kind of performance problems.  Or, at least if it is a
performance problem, it should affect the errant program and not the whole system.

So I have to put the blame on the Kernel, or maybe it it is the Unix standard.

Hopefully, this will be fixed where it needs to be fixed, which is in the Kernel.