From: maurice <mhilarius@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Looking for the best way to do this
Date: Fri, 24 Jun 2011 11:11:14 -0600 [thread overview]
Message-ID: <4E04C532.2040008@gmail.com> (raw)
In-Reply-To: <4E04C27E.7040608@cdf.toronto.edu>
On 6/24/2011 10:59 AM, Iordan Iordanov wrote:
>
> On 06/24/11 12:35, maurice wrote:
>> Set aside (disconnect) 1 of the existing 2 disks.
>> Boot from emergency recovery media, making sure the md version is
>> relatively current ( newer than 3.0 ?)
>>
>> Create the R10 with the other 2 disks ( 1 old and 1 new) with 1 of the 3
>> disks missing.
>> I think I have to wipe the superblock on the disk that was formerly part
>> of the RAID1 set.
>
> I think your procedure can be made less risky by making a R10, with
> layout f3 with *two* missing disks. Since there are *3* copies in the
> R10, there is no problem with having just one "real" disk and two
> missing ones. This way, you don't have to live with just one of the R1
> disks and hope it doesn't go bad during the copy operation.
>
> Then, you copy the data from your old R1 to your new R10 with the two
> missing disks. When the data is copied over, you can remove *one* of
> the disks from the R1, zero the superblock, and add it to the R10.
> When the rebuild is complete, and only then, zero the superblock of
> your last R1 disk, and add it to the R10.
>
> With this mod, your data never really lost redundancy during the
> entire procedure (except when you remove the first disk from the R1
> and move it to the R10, but instead of redundancy, you have 2 copies -
> one on the R10 and one on the R1 at that point, so it's still
> redundant in a way).
>
> Whether or not you use this revised procedure, write yourself a
> step-by-step guide with all the commands (a TO-DO list), and if you
> want, you can share it with the list if you're not confident.
>
Thanks, this makes really good sense, and sounds VERY safe.
As for the "TO-DO list" or "recipe" I still lack the skills to produce
the syntax.
--
Cheers,
Maurice Hilarius
eMail: /mhilarius@gmail.com/
prev parent reply other threads:[~2011-06-24 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 18:13 Looking for the best way to do this maurice
2011-06-23 1:20 ` Leslie Rhorer
2011-06-23 19:23 ` Iordan Iordanov
2011-06-23 22:06 ` maurice
2011-06-23 22:55 ` Phil Turmel
[not found] ` <4E03CBC3.1080001@gmail.com>
2011-06-23 23:41 ` Phil Turmel
2011-06-24 16:17 ` Iordan Iordanov
2011-06-24 16:35 ` maurice
2011-06-24 16:59 ` Iordan Iordanov
2011-06-24 17:11 ` maurice [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=4E04C532.2040008@gmail.com \
--to=mhilarius@gmail.com \
--cc=linux-raid@vger.kernel.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 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.