From: Jaakko Helminen <haukkari@ihme.org>
To: linux-kernel@vger.kernel.org
Subject: i/o wait eating all of CPU on 2.6.1
Date: Sun, 25 Jan 2004 16:30:42 +0200 [thread overview]
Message-ID: <20040125143042.GA20274@ihme.org> (raw)
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
next reply other threads:[~2004-01-25 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 14:30 Jaakko Helminen [this message]
2004-01-25 14:37 ` i/o wait eating all of CPU on 2.6.1 Paolo Ornati
2004-01-25 14:41 ` Jaakko Helminen
2004-01-25 15:06 ` Ed Tomlinson
2004-01-26 23:59 ` bill davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040125143042.GA20274@ihme.org \
--to=haukkari@ihme.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox