From: Bill Davidsen <davidsen@tmr.com>
To: David Rees <drees76@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID10 - migrating disks without failing/degrading array?
Date: Tue, 13 Oct 2009 18:20:36 -0400 [thread overview]
Message-ID: <4AD4FD34.4090402@tmr.com> (raw)
In-Reply-To: <72dbd3150910021122r474c43f6m2f1d953b5af9c3e0@mail.gmail.com>
David Rees wrote:
> I've got an 8 disk RAID10 array (near2 layout) where I am moving data
> off some older disks onto newer disks.
>
> Currently what I'm doing is adding the newer disks as spares and then
> failing/removing the older disks one at a time.
>
> This works fine, but leaves me with an hour or so of running the array
> degraded while the spare drive syncs up which leaves me open for
> data-loss during this time period.
>
> It seems like I should be able to add a drive as a directly
> replacement for one of the drives I'm pulling out (so I temporarily
> end up with 3-copies of that chunk instead of 2) until I pull
> fail/remove the older disk. If I was using RAID0 striped over RAID1
> mirrors, for example, I know this is possible.
>
> Is this possible to do with RAID10?
>
In a slow, ugly, complex way, as someone described in another response.
It involves using raid-1, and I suggest checking the write-mostly option
as well, and involves some short time without the 2nd copy configured
(and using check may not test everything on raid-10). Use a bitmap if
you're not already.
There is at least one other current thread regarding the need for a
"clone member" feature in md, but unless someone with time and skills
also has the problem, I doubt it's going to get added soon.
--
Bill Davidsen <davidsen@tmr.com>
Unintended results are the well-earned reward for incompetence.
prev parent reply other threads:[~2009-10-13 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 18:22 RAID10 - migrating disks without failing/degrading array? David Rees
[not found] ` <7d86ddb90910021836h537e2af6h552b7c89af37d612@mail.gmail.com>
2009-10-03 2:53 ` David Rees
2009-10-03 8:42 ` Tom Carlson
2009-10-13 22:20 ` Bill Davidsen [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=4AD4FD34.4090402@tmr.com \
--to=davidsen@tmr.com \
--cc=drees76@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 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).