linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: Pro-active replacement
Date: Sat, 14 Aug 2010 16:20:22 +0200	[thread overview]
Message-ID: <20100814142022.GA7746@lazy.lzy> (raw)

Hi all,

time to time there is the discussion about
RAID-5/6 proactive replacement of an HDD.

Reading this mailing someone suggested to
use somehow RAID-1 under the RAID-5/6.

I would like to summarize this and have some
feedback, in order to understand if this is a
feaseable way or it would be better to have it
integrated directly into the RAID-5/6.

First of all, what I understood as "proactive
replacement".

This should be the ability to add an HDD (A) to
a RAID-5/6 array, as spare and replace some other
HDD (B) without failing/removing B during the
process of resync, but only in the end.
So the array will be always, during the replacement,
fully functional with the maximum protection it can
offer (of course, until something goes wrong).

The idea would be the following.

Assuming a RAID-5 is the target, with n HDDs.

First of all, n single disk RAID-1 are created.

Second, a RAID-5 is creted using, as components,
the n RAID-1.

When a proactive replacement of HDD x is wanted,
the "spare" y is added to the correspoinding RAID-1,
i.e. the RAID-1 which is using HDD x.

After the resync of the RAID-1 takes place, the
HDD x could be failed/removed from the corresponding
RAID-1.

This should guarantee the RAID-5 has always n HDDs,
or more.

Questions:

1) Does this make sense?
2) How much performance degradation could be expected? 
3) Is there something not forseen?
4) Is there a better solution?
5) How difficult could be to integrate this into the RAID-5/6?

Thanks a lot in advance,

bye,

-- 

piergiorgio

                 reply	other threads:[~2010-08-14 14:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100814142022.GA7746@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --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).