From: Jim Paris <jim@jtan.com>
To: Mike Hardy <mhardy@h3c.com>
Cc: Kanoa Withington <kanoa@cfht.hawaii.edu>,
Huntress Gary B NPRI <HuntressGB@Npt.NUWC.Navy.Mil>,
"'linux-raid@vger.kernel.org'" <linux-raid@vger.kernel.org>
Subject: Re: High System Load
Date: Wed, 28 Jul 2004 20:17:33 -0400 [thread overview]
Message-ID: <20040729001732.GA18905@jim.sh> (raw)
In-Reply-To: <41083CB6.9070901@h3c.com>
> #!/bin/tcsh
> while 1
> cat /proc/mdstat
> sleep 1
> clear
> end
.. or just 'watch cat /proc/mdstat' :)
> There's got to be something else happening on the machine...
I find that if the kernel variable dev.raid.speed_limit_max is too
high (the default, 200000, is usually too high), then the rebuild
could taking all available I/O time. This can cause every other
process trying to do I/O on the machine to block, which may be the
reason your load average is so high.
Try doing 'sysctl -w dev.raid.speed_limit_max=10000' and see if things
improve.
-jim
prev parent reply other threads:[~2004-07-29 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 23:00 High System Load Huntress Gary B NPRI
2004-07-28 23:23 ` Kanoa Withington
2004-07-28 23:54 ` Mike Hardy
2004-07-29 0:17 ` Jim Paris [this message]
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=20040729001732.GA18905@jim.sh \
--to=jim@jtan.com \
--cc=HuntressGB@Npt.NUWC.Navy.Mil \
--cc=kanoa@cfht.hawaii.edu \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.