From: John Rowe <rowe@excc.ex.ac.uk>
To: seth vidal <skvidal@phy.duke.edu>
Cc: Mike Hardy <mhardy@h3c.com>, linux-raid@vger.kernel.org
Subject: Re: Slow reconstruction
Date: Wed, 29 Jun 2005 18:49:35 +0100 [thread overview]
Message-ID: <1120067375.21458.258.camel@volt> (raw)
In-Reply-To: <1120067215.10448.61.camel@cutter>
>
> did you raise speed_limit_min??
>
> if you didn't then you're probably being hit by the 'only use idle io'
> problem.
That's fixed it! It's now going along at around 5.7 MB/s which isn't
huge but is around 11 times what it was. Many thanks.
But I'm a bit surprised this makes a difference because there is no
other real IO going on.
John
next prev parent reply other threads:[~2005-06-29 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 16:10 Slow reconstruction John Rowe
2005-06-29 16:40 ` Mike Hardy
2005-06-29 17:31 ` John Rowe
2005-06-29 17:46 ` seth vidal
2005-06-29 17:49 ` John Rowe [this message]
2005-06-29 17:49 ` KELEMEN Peter
2005-06-29 17:52 ` John Rowe
2005-06-29 18:00 ` KELEMEN Peter
2005-06-29 17:54 ` Tyler
2005-06-29 17:32 ` seth vidal
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=1120067375.21458.258.camel@volt \
--to=rowe@excc.ex.ac.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.com \
--cc=skvidal@phy.duke.edu \
/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).