Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: Neil Brown <neilb@suse.de>
Cc: Christian <cjs@dhp.com>, linux-raid@vger.kernel.org
Subject: Re: Adding larger disks to RAID5
Date: Tue, 22 May 2007 08:15:44 -0400	[thread overview]
Message-ID: <20070522121544.GA4349@ti88.telemetry-investments.com> (raw)
In-Reply-To: <18002.15343.525501.64958@notabene.brown>

> On Monday May 21, brugolsky@telemetry-investments.com wrote:
> > One could start a RAID 4/5/6 array over a degraded RAID1 for each
> > component, (i.e., a degraded RAID1).
 
That was supposed to say "a degraded RAID5+1".

On Tue, May 22, 2007 at 10:40:15AM +1000, Neil Brown wrote:
> This doesn't really have anything to do with the metadata used - it is
> primarily an implementation issue (though you would need to be careful
> picking up the pieces after a crash).
 
Right.  Doing it all automatically would be great, but involves some
kernel work.

What I was suggesting is that one administratively stop an array
built conventionally, and manually start a degraded RAID1 for each
component.  It seems that is possible using "--build".  Then one can
manually assemble the RAID5+1 from those RAID1s, and proceed with the
disk-by-disk replacement while the array is online.  Looks as if that
ought to be possible.  I'll have to give it a try, as soon as I have an
afternoon to tinker [say, ... mid-summer :-/].

Many thanks, Neil.

	-Bill

      reply	other threads:[~2007-05-22 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 20:44 Adding larger disks to RAID5 Christian
2007-05-21 23:34 ` Neil Brown
2007-05-21 23:57   ` Bill Rugolsky Jr.
2007-05-22  0:40     ` Neil Brown
2007-05-22 12:15       ` Bill Rugolsky Jr. [this message]

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=20070522121544.GA4349@ti88.telemetry-investments.com \
    --to=brugolsky@telemetry-investments.com \
    --cc=cjs@dhp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox