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: Mon, 21 May 2007 19:57:35 -0400 [thread overview]
Message-ID: <20070521235735.GA26776@ti88.telemetry-investments.com> (raw)
In-Reply-To: <18002.11374.159035.143026@notabene.brown>
Neil,
What seems desirable to me is a way to take a new (larger) spare drive and
add it to a RAID1 for a particular RAID 4/5/6 component, and then when
it's sync'd, replace the now redundant small drive with another larger
drive. Wash, rinse, repeat. This way the array is never degraded.
Though I imagine that this particular arrangement doesn't have the
benefit of the stripe rewrite when encountering a latent error on the
drive that is being migrated. [Presumably the failing addresses could
be cycled through the check from userland though, by doing a read above
the stacked RAID.]
One could start a RAID 4/5/6 array over a degraded RAID1 for each
component, (i.e., a degraded RAID1).
I haven't been following the metadata changes closely. Is it possible
to do this with external MD metadata? It can also be done with
device-mapper, but dm-mirror is very immature compared to MD RAID1.
Comments?
Regards,
Bill Rugolsky
next prev parent reply other threads:[~2007-05-21 23:57 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. [this message]
2007-05-22 0:40 ` Neil Brown
2007-05-22 12:15 ` Bill Rugolsky Jr.
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=20070521235735.GA26776@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