All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-raid@vger.kernel.org
Subject: way too high reconstruction speed - bug?
Date: Thu, 10 Aug 2006 11:48:25 +0200	[thread overview]
Message-ID: <44DB00E9.8020000@wpkg.org> (raw)

I noticed that I have a wrong reconstruction speed when looking at 
/proc/mdstat:

# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10]
md11 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1]
       779264640 blocks super 1.0 64K chunks 2 near-copies [4/4] [UUUU]
       [===>.................]  resync = 16.4% (127955392/779264640) 
finish=4.1min speed=2588238K/sec


2588238K/sec is about 100 more to what I used to see before.


Should I start to worry?

I'm using kernel 2.6.16.27 on ARM CPU.

[42949428.580000] md: bind<sdb2>
[42949428.580000] md: bind<sdc2>
[42949428.590000] md: bind<sdd2>
[42949428.590000] md: bind<sda2>
[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.



-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2006-08-10  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  9:48 Tomasz Chmielewski [this message]
2006-08-10 18:43 ` way too high reconstruction speed - bug? Paul Clements
2006-08-11 11:47   ` Tomasz Chmielewski

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=44DB00E9.8020000@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 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.