linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: way too high reconstruction speed - bug?
Date: Fri, 11 Aug 2006 13:47:20 +0200	[thread overview]
Message-ID: <44DC6E48.7070506@wpkg.org> (raw)
In-Reply-To: <44DB7E39.4060001@steeleye.com>

Paul Clements wrote:
> Tomasz Chmielewski wrote:
>> [42949428.590000] md: md11: raid array is not clean -- starting 
>> background reconstruction
>> [42949428.620000] raid10: raid set md11 active with 4 out of 4 devices
>> [42949428.630000] md: syncing RAID array md11
>> [42949428.630000] md: minimum _guaranteed_ reconstruction speed: 1000 
>> KB/sec/disc.
>> [42949428.640000] md: using maximum available idle IO bandwidth (but 
>> not more than 200000 KB/sec) for reconstruction.
>> [42949428.650000] md: using 128k window, over a total of 779264640 
>> blocks.
>> [42949428.650000] md: resuming recovery of md11 from checkpoint.
> 
> The recovery was resumed from a previous checkpoint. I guess you 
> rebooted or stopped the array during recovery?
> 
> At any rate, md doesn't calculate resync speed correctly for 
> checkpointed or bitmapped resyncs (it assumes that the skipped portion 
> was actually resynced).
> 
> Neil fairly recently sent in patches to fix this, but I think they won't 
> be in mainline until 2.6.18 or so.

All right, thanks for explanation.

After yet another reboot I had something like speed=7588238K/sec, I can
only wonder when hard drives will have this speed :)


-- 
Tomasz Chmielewski
http://wpkg.org


      reply	other threads:[~2006-08-11 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  9:48 way too high reconstruction speed - bug? Tomasz Chmielewski
2006-08-10 18:43 ` Paul Clements
2006-08-11 11:47   ` Tomasz Chmielewski [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=44DC6E48.7070506@wpkg.org \
    --to=mangoo@wpkg.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).