From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Guy Van Sanden <n.b@myrealbox.com>
Cc: Clint Byrum <cbyrum@spamaps.org>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Heavy iowait on 2.6 kernels
Date: Wed, 16 Jun 2004 17:45:51 +1000 [thread overview]
Message-ID: <40CFFAAF.7070905@yahoo.com.au> (raw)
In-Reply-To: <1087369893.11205.36.camel@cronos.home.vsb>
Guy Van Sanden wrote:
> My machine is heavily used for all kinds of file serving (mainly nfs),
> but also samba.
> Next to that, it is my home-server, so it runs apache2 (tuned to server
> only few clients), imap (cyrus), postfix, bugzilla (mysql) and distcc
> (used only a few times a week).
> It replaces a FreeBSD system (PII-333) running the same except distcc.
> Under
>
> The disk system is just a regular IDE disk (udma5) (60GB) and one
> external drive over USB2 (160 GB). The external drive is rather slow
> (20-30 MB/sec), so I disabled it during the tests.
>
> The weird thing is that I see this problem too when only running bonnie.
> A friend of mine tried that too under 2.6.6, his iowait went up to
> 0.15%, mine to 99%.
>
The CPU can very easily max out the disks of course. If bonnie is
doing IO to files much larger than memory, it wouldn't be surprising
for io-wait to get close to 100%. Possibly your friend was doing all
IO out of cache?
If you definitely have a performance problem, set "Kernel Debugging"
on in the "Kernel Hacking" menu, then set "Magic SysRq key" on. When
your system hits this iowait problem, press Alt+SysRq+T a couple of
times over a few seconds.
Then post the output of `dmesg -s 1000000`.
We'll see what is waiting where.
next prev parent reply other threads:[~2004-06-16 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 8:35 PROBLEM: Heavy iowait on 2.6 kernels Guy Van Sanden
2004-06-12 6:31 ` Nick Piggin
2004-06-16 6:15 ` Clint Byrum
2004-06-16 7:25 ` Guy Van Sanden
2004-06-16 7:45 ` Nick Piggin [this message]
2004-06-16 12:21 ` Guy Van Sanden
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=40CFFAAF.7070905@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=cbyrum@spamaps.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n.b@myrealbox.com \
/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