Re: i/o wait eating all of CPU on 2.6.1

From: Ed Tomlinson
Date: Sun Jan 25 2004 - 10:08:30 EST


Hi,

A couple of things. IO wait does not 'eat cpu'. Its a wait state, recorded
when the box has nothing to do and IO is pending. That being said I remember
reading here about nfs bugs in 2.6.1 that slow it down. A search should
find some patches for you to try.

Ed

On January 25, 2004 09:30 am, Jaakko Helminen wrote:
> I have two servers, both of which have more than 300 gigabytes of hard
> drive space and those files are made available to the network with samba,
> nfs and http and it worked fine with 2.6.0 but when I upgraded to 2.6.1 I
> noticed that everything was VERY slow, from a machine that is connected to
> the other server with a 100M link, 57kB/s tops. i/o wait eats up all of the
> cpu. On the other hand, Apache (and everything else) works very fast when I
> only send /dev/zero to a client, since that doesn't need disk operations.
>
> I don't notice anything suspicious in dmesg but since this happens on two
> machines and has only happened when upgraded to 2.6.1, it's most likely
> because of 2.6.1. I'm downgrading to 2.6.0 (with mremap-patch) today if I
> don't figure out what is wrong. Any ideas?
>
> And since I'm not subscribed to Linux Kernel Mailing List, please forward
> any replies to me.
>
>
> -Jaakko Helminen
>
> -
> 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/
-
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/