All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 resize in 2.6.17 - how will it be different from raidreconf?
Date: Mon, 22 May 2006 13:17:36 +0200	[thread overview]
Message-ID: <200605221317.37083.Dexter.Filmore@gmx.de> (raw)
In-Reply-To: <17520.61194.529436.322401@cse.unsw.edu.au>

> > Will it be less risky to grow an array that way?
>
> It should be.  In particular it will survive an unexpected reboot (as
> long as you don't lose and drives at the same time) which I don't
> think raidreconf would.
> Testing results so far are quite positive.

Write cache comes to mind - did you test power fail scenarios?

> > (And while talking of that: can I add for example two disks and grow
> > *and* migrate to raid6 in one sweep or will I have to go raid6 and then
> > add more disks?)
>
> Adding two disks would be the preferred way to do it.
> Add only one disk and going to raid6 is problematic because the
> reshape process will be over-writing live data the whole time, making
> crash protection quite expensive.
> By contrast, when you are expanding the size of the array, after the
> first few stripes you are writing to an area of the drives where there
> is no live data.

Let me see if I got this right: if I add *two* disks and go from raid 5 to 6 
with raidreconf, no live data needs to be overwritten and in case something 
fails I will still be able to assemble the "old" array..?


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C+++(++++) UL+>++++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS++(+) PE(-) Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D G++ e* h>++ r%>* y?
------END GEEK CODE BLOCK------

http://www.stop1984.com
http://www.againsttcpa.com

  reply	other threads:[~2006-05-22 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 22:34 raid5 resize in 2.6.17 - how will it be different from raidreconf? Dexter Filmore
2006-05-21 22:51 ` Neil Brown
2006-05-22 11:17   ` Dexter Filmore [this message]
2006-05-22 11:34     ` Neil Brown

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=200605221317.37083.Dexter.Filmore@gmx.de \
    --to=dexter.filmore@gmx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.