From: Bill Davidsen <davidsen@tmr.com>
To: "Eric S. Johansson" <esj@harvee.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: I/O wait problem with hardware raid
Date: Sat, 30 Aug 2008 14:47:21 -0400 [thread overview]
Message-ID: <48B995B9.2040600@tmr.com> (raw)
In-Reply-To: <48B75097.7000509@harvee.org>
Eric S. Johansson wrote:
> I'm not sure if this mailing lists is just for the Linux kernel raid so this
> query does not belong, feel free to tell me where to go.
>
> I'm running Ubuntu 8.04 on an HP ProLiant ml350 with an E200i sata raid card.
>
> The problem is the I/O wait percentage increases during data transfer. A simple
> rsync transfer will bring the percent I/O wait value up to the mid-20s to 40s
> and a little more stress causes the wait percentage to climb to upper 90% range.
> it appears that most of the I/O wait time is from the disk array because a copy
> has a similar effect. However, I cannot eliminate some contribution by the
> networking code.
>
> I'm not sure how to debug this. vmstat doesn't show anything extraordinary so
> I'm left scratching my head.
>
> what should I be looking for?
>
iowait means that there is a program waiting for I/O. That's all. Of
course when you do a copy (regardless of software) the CPU is waiting
for disk transfers. I'm not sure what you think you should debug, i/o
takes time, and if the program is blocked until the next input comes in
it will enter the waitio state. If there is no other process to use the
available CPU it becomes waitio, which is essentially available CPU
cycles similar to idle.
What exactly do you think is wrong?
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-08-30 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 1:27 I/O wait problem with hardware raid Eric S. Johansson
2008-08-30 18:47 ` Bill Davidsen [this message]
2008-08-31 14:50 ` Eric S. Johansson
2008-08-31 15:48 ` Roger Heflin
2008-08-31 21:08 ` 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=48B995B9.2040600@tmr.com \
--to=davidsen@tmr.com \
--cc=esj@harvee.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).