From: Durval Menezes <durval.menezes@gmail.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Maximizing failed disk replacement on a RAID5 array
Date: Mon, 13 Jun 2011 02:32:47 -0300 [thread overview]
Message-ID: <BANLkTikqs6R9r9hRAPR5b4ErLf1xr8yBpQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin8dpbxWfSCG_VoOM_FMmqCkm2mJg@mail.gmail.com>
Hello Folks,
On Wed, Jun 8, 2011 at 10:21 AM, Brad Campbell
<lists2009@fnarfbargle.com> wrote:
>
> Best of luck, and let us know how you get on.
Just finished the process here. To summarize, seems I've got my array
back in a stable state.
What I did:
1) Got a good backup of all the data in the array (using "tar") to
removable HDs, verified it (using md5sum), and then stored these
HDs safely offline;
2) Unmounted the filesystem in the array;
3) inserted the replacement disk on a USB dock, partitioned it,
then added it to the array ("mdadm --add");
-> Verified (via "mdadm --detail") that the replacement disk was
listed on the array as a "spare";
4) failed the bad disk in the array ("mdadm --fail")
-> At that point, the array immediatelly started to resync into the
replacement disk;
5) Monitored the resync process via "cat /proc/mdstat": it took
roughly 11 hours (I guess because transfer speed to the replacement
disk was limited by the USB ~40MB/s speed limit), but it signaled
no errors;
6) Verified that the array was really synced ("mdadm --detail") and
that there were indeed no errors during the resync (less
/var/log/messages);
7) removed the bad disk logically from the array ("mdadm --remove");
8) shut down the machine (init 0);
9) removed the bad disk physically from the machine, ejected the
replacement disk from the USB dock, and then installed the
replacement disk inside the machine;
10) turned the system on: the OS booted, assembled the array and
mounted the filesystem in it with no issues;
11) checked (using "md5sum -c" on the md5sum files generated during
pass#1 above) that all that ON THE ARRAY was indeed correct, so
in the end I didn't need to restore anything from backup.
Thanks for all the help, folks, and I pray we have the "hot-replace"
functionality implemented soon... it will make for much sounder sleep
the next time one of my disks fails... :-)
Cheers,
--
Durval Menezes.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-13 5:32 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
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 [this message]
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=BANLkTikqs6R9r9hRAPR5b4ErLf1xr8yBpQ@mail.gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.