From: Drew <drew.kay@gmail.com>
To: Durval Menezes <durval.menezes@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Maximizing failed disk replacement on a RAID5 array
Date: Mon, 6 Jun 2011 08:02:48 -0700 [thread overview]
Message-ID: <BANLkTi=px08AWxfJJq+zNepCZM8aAsKECA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimOxCF7diZfeFgtqCBWKZVF2pxyLg@mail.gmail.com>
> I understand that, if I do it the "standard" way (ie, power down the
> system, remove the failing disk, add the replacement disk, then boot
> up and use "mdadm --add" to add the new disk to the array) I run the
> risk of running into unreadable sectors on one of the other two disks,
> and then my RAID5 is kaput.
>
> What I would really like to do is to be able to add the new HD to the
> array WITHOUT removing the failing HD, somehow sync it with the rest,
> and THEN remove the failing HD: that way, an eventual failed read from
> one of the two other HDs could possibly be satisfied from the failing
> HD (unless EXACTLY that same sector is also unreadable on it, which I
> find unlikely), and so avoid losing the whole array in the above case.
A reshape from RAID5 -> RAID6 -> RAID5 will hammer your disks so if
either of the other two are ready to die, this will most likely tip
them over the edge.
A far simpler way would be to take the array offline, dd (or
dd_rescue) the old drive's contents onto the new disk, pull the old
disk, and restart the array with the new drive in it's place. With
luck you won't need a resync *and* you're not hammering the other two
drives in the process.
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
"This started out as a hobby and spun horribly out of control."
-Unknown
next prev parent reply other threads:[~2011-06-06 15:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimBYFhjQ-sC9DhTMO+PG-Ox+A9S2Q@mail.gmail.com>
2011-06-05 14:22 ` Fwd: Maximizing failed disk replacement on a RAID5 array Durval Menezes
2011-06-06 15:02 ` Drew [this message]
2011-06-06 15:20 ` Brad Campbell
2011-06-06 15:37 ` Drew
2011-06-06 15:54 ` Brad Campbell
2011-06-06 18:06 ` Durval Menezes
2011-06-07 5:03 ` Durval Menezes
2011-06-07 5:35 ` Brad Campbell
2011-06-08 6:58 ` Durval Menezes
2011-06-08 7:32 ` Brad Campbell
2011-06-08 7:47 ` Durval Menezes
2011-06-08 7:57 ` Brad Campbell
[not found] ` <BANLkTi=BuXK4SBGR=FrEcHFC1WohNkUY7g@mail.gmail.com>
[not found] ` <4DEF7775.5020407@fnarfbargle.com>
[not found] ` <BANLkTin8dpbxWfSCG_VoOM_FMmqCkm2mJg@mail.gmail.com>
2011-06-13 5:32 ` Durval Menezes
2011-06-13 5:56 ` Durval Menezes
2011-06-07 8:52 ` John Robinson
2011-06-10 10:25 ` John Robinson
2011-06-11 22:35 ` Durval Menezes
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='BANLkTi=px08AWxfJJq+zNepCZM8aAsKECA@mail.gmail.com' \
--to=drew.kay@gmail.com \
--cc=durval.menezes@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).