linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Gilad Arnold <arnold@cs.berkeley.edu>
Cc: Bill Davidsen <davidsen@tmr.com>, Roman Mamedov <roman@rm.pp.ru>,
	linux-raid@vger.kernel.org
Subject: Re: migrating from RAID5 to RAID10
Date: Fri, 18 Jun 2010 12:39:10 +1000	[thread overview]
Message-ID: <20100618123910.711b527b@notabene.brown> (raw)
In-Reply-To: <20100617224657.GD8450@libra.CS.Berkeley.EDU>

On Thu, 17 Jun 2010 15:46:57 -0700
Gilad Arnold <arnold@cs.berkeley.edu> wrote:

> On Thu, Jun 17, 2010 at 10:44:45AM -0700, Gilad Arnold wrote:
> > This leads me to think that even with 2 drives, RAID10/f2 is a better
> > choice than RAID1. Is this a fair assessment?
> 
> Okay, I found the benchmarks that support this hypothesis ;-)
> 
> > And, if it is the case, can RAID5 be converted to RAID10/f2
> > on-the-fly, or would I have to take the longer path?  (i.e. degrade
> > RAID5, start RAID10 in degraded mode, copy data, kill RAID5 and
> > rebuild RAID10)
> 
> Some more reading leads me to think that on-the-fly RAID5 to RAID10/f2
> conversion wouldn't work.  However, I'm tempted to believe that I can
> avoid the data copy phase entirely and skip straight to RAID10 rebuild:
> 
> 1. Shutdown the RAID5.
> 
> 2. Create a RAID10/f2 on top of one drive + missing, ignoring mdadm's
>    warnings about an existing array. If I'm not terribly wrong, this
>    will give me a degraded RAID10 that still has all my data in place.

I cannot imagine why you would think that all your data would be in place.
I can assure that it would not.

NeilBrown

> 
> 3. Add the second drive to the RAID10 and watch it rebuild.
> 
> 
> Apologies for my petty questions ;-)  Advice appreciated.
> 
> Gilad


  reply	other threads:[~2010-06-18  2:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 15:11 migrating from RAID5 to RAID10 Gilad Arnold
2010-06-10 18:52 ` Roman Mamedov
2010-06-10 19:58   ` Gilad Arnold
2010-06-10 22:11     ` Drew
2010-06-10 22:21       ` Drew
2010-06-10 22:30         ` Gilad Arnold
2010-06-10 22:26       ` Gilad Arnold
2010-06-16 15:54     ` Bill Davidsen
2010-06-16 18:30       ` Gilad Arnold
2010-06-16 20:15         ` Gilad Arnold
2010-06-17  1:59           ` Bill Davidsen
2010-06-16 21:26       ` Neil Brown
2010-06-17 17:44         ` Gilad Arnold
2010-06-17 22:30           ` Neil Brown
2010-06-18  8:40             ` Keld Simonsen
2010-06-21 22:09               ` Neil Brown
2010-06-17 22:46           ` Gilad Arnold
2010-06-18  2:39             ` Neil Brown [this message]
2010-06-18  4:01               ` Gilad Arnold

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=20100618123910.711b527b@notabene.brown \
    --to=neilb@suse.de \
    --cc=arnold@cs.berkeley.edu \
    --cc=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=roman@rm.pp.ru \
    /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).