linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Burgess <aab@cichlid.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid sync observations
Date: Tue, 20 Dec 2005 10:27:41 -0800	[thread overview]
Message-ID: <200512201827.jBKIRf6m019390@cichlid.com> (raw)

>I just created a RAID array (4-disk RAID-6).  When "mdadm -C" returned,
>/proc/mdstat showed it syncing the new array at about 17 MB/s.  "vmstat 1"
>showed hardly any blocks in or out, and an almost completely idle cpu.

>Question 1: Why didnt the raid sync I/O show up with vmstat?

I switched to iostat because of similar observations with vmstat. iostat
at least shows you which devices it is looking at and it agrees with
/proc/mdstat's numbers in my experience.

>Question 2: Why was it limited to 17 MB per second?  The maximum was
>left at the default, 200 MB/s.  The min was also at the default, 1 MB/s.
>I get 60 MB/s per disk with "hdparm -tT" (that's using one disk at a time,
>but still).  The checksumming code does > 3 GB/s.

Try using dd to read each device in parallel as it might be a bus or controller
limitation. Also, sync requires writing interspersed with the reads which
unavoidably ruins the total throughput. Larger stripes should minimize this if
you think it'll be a problem during everyday use.


             reply	other threads:[~2005-12-20 18:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 18:27 Andrew Burgess [this message]
2005-12-20 19:13 ` Raid sync observations Sebastian Kuzminsky
  -- strict thread matches above, loose matches on Subject: below --
2005-12-20 22:09 Jeff Breidenbach
2005-12-20 17:18 Sebastian Kuzminsky
2005-12-20 18:14 ` Sebastian Kuzminsky
2005-12-20 21:27 ` Neil Brown
2005-12-20 21:33   ` Sebastian Kuzminsky
2005-12-21  1:55 ` Christopher Smith
2005-12-21 11:49   ` Andy Smith
2005-12-21 17:02     ` Sebastian Kuzminsky
2005-12-21 17:13       ` Gordon Henderson
2006-01-08 18:18         ` Bill Davidsen

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=200512201827.jBKIRf6m019390@cichlid.com \
    --to=aab@cichlid.com \
    --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).