linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Evans <mjevans1983@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 5 build time optimization question and experiments.
Date: Fri, 11 Dec 2009 14:35:22 -0800	[thread overview]
Message-ID: <4877c76c0912111435o5a79dfccs2a27b48128150921@mail.gmail.com> (raw)
In-Reply-To: <ad15b8920912110857y12e0df7bqe076ba42fee0102d@mail.gmail.com>

On Fri, Dec 11, 2009 at 8:57 AM, Cat'Killer <catkiller@gmail.com> wrote:
>> On Fri Dec 11, 2009 at 02:55:31PM +0000, Cat'Killer wrote:
>>
>>> I found a way using Doug Gilbert's great sg3utils to zero all these
>>> disks in a very efficient manner, using sgp_dd, at near drive
>>> bandwidth, and proceeded to zero all the disks fully in about 4 hours!
>>>
>>> Once done, I then created a RAID 5 on 10 disks, waited for the rebuild
>>> to complete, stopped the array using mdadm, and dumped each of the
>>> RAID's components superblocks to files.
>>>
>> <-snip->
>>>
>>> The create worked fine and I waited for the rebuild to be complete
>>> before stopping the array and dumping the SBs.
>>>
>>> I then proceeded to write these same superblocks to 10 new similar
>>> disks in a different system.
>>>
>> You could just do the create with --assume-clean, which should take very
>> little time at all.  If the drives were zeroed initially then this will
>> give you valid parity data.
>>
> Thank you for this, that's exactly what I was looking for. I had
> looked in the manpage beforehand but I did not search for the right
> terms nor assumed this would work in case of an array created ontop of
> zeroed drives.
>
> Thanks again.
>
> Ben.
>
>> Cheers,
>>   Robin
>>
>> --
>>    ___           ( ' }     |       Robin Hill        <robin@robinhill.me.uk>
>> |
>>  / / )      | Little Jim says ....                            |
>>  // !!       |      "He fallen in de water !!"                 |
>>
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Yes, I had just come to a similar conclusion in a recent email series
and even provided a patch against the git copy of the manpage to
clarify the documentation.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-12-11 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B227932.80503@mpstor.com>
2009-12-11 16:57 ` RAID 5 build time optimization question and experiments Cat'Killer
2009-12-11 22:35   ` Michael Evans [this message]
2009-12-11 14:55 Cat'Killer
2009-12-11 15:29 ` Robin Hill
2009-12-11 15:44   ` Joe Landman

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=4877c76c0912111435o5a79dfccs2a27b48128150921@mail.gmail.com \
    --to=mjevans1983@gmail.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).