From: Bill Davidsen <davidsen@tmr.com>
To: Gilad Arnold <arnold@cs.berkeley.edu>
Cc: Roman Mamedov <roman@rm.pp.ru>, linux-raid@vger.kernel.org
Subject: Re: migrating from RAID5 to RAID10
Date: Wed, 16 Jun 2010 11:54:06 -0400 [thread overview]
Message-ID: <4C18F39E.8010600@tmr.com> (raw)
In-Reply-To: <20100610195851.GA8408@libra.CS.Berkeley.EDU>
Gilad Arnold wrote:
> Thanks for your response, Roman.
>
> On Fri, Jun 11, 2010 at 12:52:30AM +0600, Roman Mamedov wrote:
>
>>> I have been using RAID5 on a desktop machine using a couple of 500
>>> GB drives. My original intent was to grow the array by adding more
>>> drives, as the need arises.
>>>
>> Do you currently run RAID5 with just 2 drives, in degraded mode, or
>> maybe you meant something else?
>>
>
> No, it is not degraded, it's a clean 2-drive RAID5. I know it doesn't
> make much sense as it is ;-) the intent was to grow the array later,
> relying on mdadm's grow feature. Right now, I'm guessing that it
> operates like a RAID1 for all practical purposes.
>
>
I have the feeling that you will then get a lot of read, alter, rewrite
(RAW) operations on the parity chuck, where you would just get writes of
a copy for raid{1,10} configuration. The performance of raid5 is poor,
but with 4-5 drives it gives you some fault tolerance. With even three
drives the write performance is poor by algorithm, and the read
performance is poor by implementation (I see no reason for reading at
the speed of just one drive).
I think your upgrade will fail, but feel free to see if a two drive
raid5 will start with only one drive, I could be wrong.
If it were me, I would leave the raid up, install the new drive, and
just copy the data to it. That way you have error tolerance on the
original data, while your method doesn't. After doing that and reading
the entire new drive to be sure it's valid, configure the two original
drives as a degraded three drive raid10. After that's done AND TESTED to
see that the data are still all valid, then you add the new drive to the
raid10 and get full operation.
Actually, if it were me I'd have a backup, too. And be damn sure to run
on a UPS.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
next prev parent reply other threads:[~2010-06-16 15:54 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 [this message]
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
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=4C18F39E.8010600@tmr.com \
--to=davidsen@tmr.com \
--cc=arnold@cs.berkeley.edu \
--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).