From: maurice <mhilarius@gmail.com>
To: Iordan Iordanov <iordan@cdf.toronto.edu>
Cc: maurice <mhilarius@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Looking for the best way to do this
Date: Fri, 24 Jun 2011 10:35:27 -0600 [thread overview]
Message-ID: <4E04BCCF.9000604@gmail.com> (raw)
In-Reply-To: <4E04B8A9.1050502@cdf.toronto.edu>
On 6/24/2011 10:17 AM, Iordan Iordanov wrote:
> Hi Maurice,
> ..
> R10 has different layouts. There are two components to the layout -
> where the chunks are located on the different devices (near, offset,
> far), and number of copies of the data. The near/offset/far part of
> the layout does not play a role in reliability, just in performance.
> So, the number of copies is the only thing that matters to this
> discussion.
>
> If you have R10 with 3 disks and 3 copies, it is equally reliable to
> R1 with 3 disks, as they have an equal number of copies. In both R10
> and R1 in this case, two disks can fail, and you still have 1 intact
> copy remaining.
>
From what I read, assuming I want to optimize this for READ
performance, I would want "R10 far".
As I understand this, if I wanted the R10, I could set aside one disk of
the R1 with my existing data,
and use on of the old disks, along with the new one, to create the R10 ?
I believe the way to accomplish this is as follows:
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.
Reconnect the old R1 reserved disk.
Copy the data from the single member of the old R1 to the new R10
On the old disk of the R1 set wipe the superblock.
Lastly add the 3rd disk to the R10 set.
Run grub to put the boot block on all 3 of the disks.
Assuming that this sequence is correct, what I need now is the correct
syntx for these steps.
Or, perhaps, I have it wrong!
--
Cheers,
Maurice Hilarius
eMail: /mhilarius@gmail.com/
next prev parent reply other threads:[~2011-06-24 16:35 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 [this message]
2011-06-24 16:59 ` Iordan Iordanov
2011-06-24 17:11 ` maurice
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=4E04BCCF.9000604@gmail.com \
--to=mhilarius@gmail.com \
--cc=iordan@cdf.toronto.edu \
--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 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).