RAID1 iowait slow writes
Date: Fri Jun 15 2007 - 19:01:21 EST
I have six identical ATA6 drives in my linux 22.214.171.124 kernel machine.
It is an AMD64 3500 with 2 GB of RAM. There are 3 IDE controllers
(onboard nForce3 IDE, PCI HPT370, and PCI PDC20269). All drives are
masters on lone cables. There are three RAID1 arrays, one on the
drives attached to the NFORCE3 controller, and two staggered across
the HPT370 and PDC20269. DMA is on.
For comparison, I can copy a 1.5GB file in 2 minutes across a single
disk on a different machine. This takes ~3-4 minutes on the software
RAID system. I am expecting 40MB/s on my six ATA6 drives (guessed from
I did this while monitoring using iostat. First, a read runs at around
50MB/s on md1 with half on component drives hda & hdc. While this
happens, sporadic writes to the destination occur at a much lower
throughput (no staggered writes on RAID1). After the 1.5GB entire file
is read (cached) into memory, md2 (the destination RAID) shows a very
high kB_wrtn/s for a few seconds. Then, the destination drives in md2
show a low speed write at ~16MB/s for a long time. The top command
shows a high iowait during all these reads and writes.
This characterizes what I've been seeing during long chains of file
i/o operations on the system. Doing stuff like copying a source tree
and checking CVS out to the local disk causes similar slowdowns.
Should the kernel be caching the entire file during the read, and then
slowly writing it out? I believe the whole thing is cached because a
second cp on a large file immediately exits while the RAID subsystem
writes it at slow speed with no reads.
Do you think this has to do with PCI bus saturation?
- Jate Sujjavanich
Please cc me on reply
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/