linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: about raid5 recovery when created
Date: Tue, 8 Dec 2009 13:14:46 +0000	[thread overview]
Message-ID: <20091208131446.GA21130@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <389deec70912080501u6c6bc90ei2d34ef245a1dae9e@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

On Tue Dec 08, 2009 at 09:01:23PM +0800, hank peng wrote:

> Hi, all:
> As we know, when a raid5 array is created, recovery will be going on
> which involves some read, one xor and one write. Since there is no
> real data in the disk at the time, besides, if I am willing to wait
> for recovery to complete and then use this raid5, how about adding
> support for a fast recovery method? Right now, what is in my mind is
> zero all disks which belong to this raid5. I think it will increase
> raid5 recovery speed when created and decrease CPU usage, since all
> zero is also XORed.
> What do raid developers think?
> 
It'll decrease CPU usage but increase I/O - you're now needing to write
to all disks.  Most systems will be I/O limited rather than CPU limited,
so the current approach works better.  If you want to zero the disks
then do this before creating the array - you can then use --assume-clean
to skip the resync process.

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-12-08 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 13:01 about raid5 recovery when created hank peng
2009-12-08 13:14 ` Robin Hill [this message]
2009-12-08 13:49   ` hank peng
2009-12-08 13:56     ` Robin Hill
2009-12-08 14:03       ` hank peng
2009-12-09  8:30         ` Michael Evans
2009-12-09 11:29           ` hank peng
2009-12-10  1:43             ` Neil Brown
2009-12-10  3:34               ` Michael Evans
2009-12-10  3:59                 ` Neil Brown
     [not found]                   ` <g3143w7eigolu0x2ziUYAxe124vaj_firegpg@mail.gmail.com>
2009-12-30  2:55                     ` Neil Brown
     [not found]           ` <389deec70912090330l73d04696v1d23dbe74423d15b@mail.gmail.com>
2009-12-09 23:29             ` Michael Evans
2009-12-08 13:52   ` hank peng

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=20091208131446.GA21130@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --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).