Re: [ext3][kernels >= 184.108.40.206 at least] KDE going comatose when FSis under heavy write load (massive starvation)
From: Linus Torvalds
Date: Fri Apr 27 2007 - 11:31:35 EST
On Fri, 27 Apr 2007, Marat Buharov wrote:
> On 4/27/07, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> > Aside: why the heck do applications think that their data is so important
> > that they need to fsync it all the time. I used to run a kernel on my
> > laptop which had "return 0;" at the top of fsync() and fdatasync(). Most
> > pleasurable.
> So, if having fake fsync() and fdatasync() is pleasurable for laptop
> and desktop, may be it's time to add option into Kconfig which
> disables normal fsync behaviour in favor of robust desktop?
This really is an ext3 issue, not "fsync()".
On a good filesystem, when you do "fsync()" on a file, nothing at all
happens to any other files. On ext3, it seems to sync the global journal,
which means that just about *everything* that writes even a single byte
(well, at least anything journalled, which would be all the normal
directory ops etc) to disk will just *stop* dead cold!
It's horrid. And it really is ext3, not "fsync()".
I used to run reiserfs, and it had its problems, but this was the
"feature" of ext3 that I've disliked most. If you run a MUA with local
mail, it will do fsync's for most things, and things really hickup if you
are doing some other writes at the same time. In contrast, with reiser, if
you did a big untar or some other big write, if somebody fsync'ed a small
file, it wasn't even a blip on the radar - the fsync would sync just that
Maybe I'm wrong on the exact details (I'm not really up on the ext3
journal handling ;^), but you don't even have to know about any internals
at all: you can just test it. Gaak.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/