linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Kuzminsky <seb@highlab.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid sync observations
Date: Tue, 20 Dec 2005 14:33:58 -0700	[thread overview]
Message-ID: <E1Eop7O-00005k-JG@highlab.com> (raw)
In-Reply-To: <17320.30528.417691.57401@cse.unsw.edu.au>

Neil Brown <neilb@suse.de> wrote:
>  You can get better speed on creation with
>    mdadm -C -l6 -n4 -x2 /dev/sd[ab] missing missing /dev/sd[cd]
> 
>  i.e. create with 2 missing devices and 2 spares.  Recovery onto the
>  spares will do purely sequential IO on all devices and so will go
>  much faster.
>  Doing this requires regenerating datablocks which is more cpu
>  intensive that generating P and Q, so there might be some CPU
>  overhead, but the disk throughput is still much faster.
> 
>  In 2.6.16, raid6 resync has been improved somewhat.  This will not
>  affect the initial sync, but resync after a crash will only write
>  P/Q blocks which are wrong and there are usually very few of those.
>  This means that it will mostly to sequential reads on all drives, so
>  you get full device speed.

Thanks!!


-- 
Sebastian Kuzminsky

  reply	other threads:[~2005-12-20 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 17:18 Raid sync observations Sebastian Kuzminsky
2005-12-20 18:14 ` Sebastian Kuzminsky
2005-12-20 21:27 ` Neil Brown
2005-12-20 21:33   ` Sebastian Kuzminsky [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2005-12-20 18:27 Andrew Burgess
2005-12-20 19:13 ` Sebastian Kuzminsky
2005-12-20 22:09 Jeff Breidenbach

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=E1Eop7O-00005k-JG@highlab.com \
    --to=seb@highlab.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).