Sure looks like ext3.
>
> Is it possible that the darn thing is mounted ext3 even though fstab and mount
> agree that it's ext2?
Yes. Although it's usually the other way round. "How come it keeps running
fsck even though mount says ext3?".
Take a look in /proc/mounts.
> > How long does
> >
> > dd if=/dev/zero of=foo bs=1M count=600 ; sync
> >
> > take against that disk?
>
> 1m 23s (I said it was a slow disk ;)
gack. I've seen pencils which can write faster than that.
So your wirespeed actually exceeds the disk speed. That changes things.
The kernel *has* to stall the generator of dirty data. We can make
the stalls shorter, and more frequent. Go into drivers/block/ll_rw_blk.c
and see where it's initialising batch_requests. Just change it to
batch_requests = 1;
batch_requests needs to die anyhow...
And in fs/mpage.c, set RATELIMIT_PAGES to 16.
The application has to block, but the disk should certainly never
fall idle. I'll play with this a bit. IDE ceased to be an option
in 2.5.30, which does not aid this effort.
> I've been trying these sorts of tests on this machine for over a year now,
> with various disk subsystems, and I have *never* seen anything as nice and
> consistent as the ext2 writeout you quoted. Maybe this machine is cursed.
>
Lumpy writeback is pretty common. As is bad latency during writeout.
It's quite tricky to get these things balanced out, and it's easy to
fix one thing and break another. Not a lot of effort has been put into
fine tuning 2.5 for smoothness and latency thus far.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/