From: seth vidal <skvidal@phy.duke.edu>
To: mjstumpf@pobox.com
Cc: linux-raid@vger.kernel.org
Subject: Re: reconstruction -- where is the upper bound?
Date: 28 Oct 2003 14:58:34 -0500 [thread overview]
Message-ID: <1067371114.24429.42.camel@opus> (raw)
In-Reply-To: <bWpzdHVtcGY=.2225bde2e3ae0856f1ad7359480d334c@1067370925.cotse.net>
On Tue, 2003-10-28 at 14:55, mjstumpf wrote:
> I'm considering my options; currently I've got a server running on a
> p2-400. What causes the upper bound--IO bandwidth or CPU speed--with
> regard to reconstruction of an array (say, a failed drive)?
>
> I forget the numbers I usually see, because I do this a lot. But it seems
> to me it has more to do with IO bandwidth than CPU horsepower. I've done
> this with both SCSI and ATA, but currently I'm referring to an ATA system.
>
> True?
>
> Is there anything I can do to speed this up
cd /proc/sys/dev/raid/
cat speed_limit_max
echo numberinKB/s > speed_limit_max
-sv
prev parent reply other threads:[~2003-10-28 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 19:55 reconstruction -- where is the upper bound? mjstumpf
2003-10-28 19:58 ` seth vidal [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=1067371114.24429.42.camel@opus \
--to=skvidal@phy.duke.edu \
--cc=linux-raid@vger.kernel.org \
--cc=mjstumpf@pobox.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;
as well as URLs for NNTP newsgroup(s).