public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Raid 5 creation is slow - Can this be done quicker?
Date: Mon, 1 Feb 2010 15:45:45 +0100	[thread overview]
Message-ID: <201002011545.45816.joost@antarean.org> (raw)
In-Reply-To: <45D49DDE-E5D2-4FDA-8B4D-7470AAC4B39D@stellar.eclipse.co.uk>

On Monday 01 February 2010 14:20:28 Stroller wrote:
> On 1 Feb 2010, at 11:58, J. Roeleveld wrote:
> > ...
> > I am currently installing a new server and am using Linux software
> > raid to
> > merge 6 * 1.5TB drives in a RAID5 configuration.
> >
> > Creating the RAID5 takes over 20 hours (according to " cat /proc/
> > mdstat ")
> >
> > Is there a way that will speed this up? The drives are new, but
> > contain random
> > data left over from some speed and reliability tests I did. I don't
> > care about
> > keeping the current 'data', as long as when the array is reliable
> > later.
> >
> > Can I use the " --assume-clean " option with mdadm and then expect
> > it to keep
> > working, even through reboots?
> > Or is this a really bad idea?
> 
> It wasn't my intention to chide you - I don't use software RAID
> myself, and your question piqued my curiosity - but the first three
> Google hits for "assume-clean" indicate that this isn't safe to use
> with RAID5.
> 
> The 4th Google hit contains an extract from the manpage:
> 
>                ... It can
>                also be used when creating a RAID1 or RAID10 if you want
>                to avoid the initial resync, however this practice --
>                while normally safe -- is not recommended. Use this
>                only if you really know what you are doing.

I did find the same results on Google, but not really a proper explanation as 
to why it's a "bad idea". Unfortunately, my budget doesn't extend to a 
hardware raid solution. (The cheap cards offload it to the CPU anyway and are 
generally considered slower in various benchmarks)

> I kinda expected this 20 hours to be spent verifying that the disks
> contain no bad sectors, which would really hose you if it were the case.

True, but I already ran "badblocks" twice on each disk to verify that the 
disks are fine. (No badblocks found).

> But OTOH, 20 hours does not seem an outrageous amount of time for
> building a 7.5TB array. You're not going to do this often, and you
> want it done right.

Good point, and I agree, which is why I will let it finish it's course, but I 
also expected it could be done quicker.

> It would be interesting to know whether hardware RAID would behave any
> differently or allow the sync to perform in the background. I have
> only 1.5TB in RAID5 across 4 x 500gb drives at present; IIRC the
> expansion from 3 x drives took some hours, but I can't recall the
> initial setup.

I'm hoping someone with more knowledge about RAID-systems can throw in his/her 
2cents.

Thanks,

Joost



  reply	other threads:[~2010-02-01 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 11:58 [gentoo-user] Raid 5 creation is slow - Can this be done quicker? J. Roeleveld
2010-02-01 13:01 ` Kyle Bader
2010-02-01 13:20 ` Stroller
2010-02-01 14:45   ` J. Roeleveld [this message]
2010-02-01 15:53     ` Kyle Bader
2010-02-08 11:23 ` [gentoo-user] Raid 5 creation is slow - Can this be done quicker? [SOLVED] J. Roeleveld

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=201002011545.45816.joost@antarean.org \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.gentoo.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