From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-raid@vger.kernel.org
Subject: Raid 5 rebuild and Raid 6 reshape question
Date: Fri, 17 Apr 2015 11:55 -0600 [thread overview]
Message-ID: <6744821.j7csV3RJVE@balsa> (raw)
This is a potentially dumb question...
I had a 5 disk Raid5 with 3TB disks. One disk threw some errors (but still
seemed to work), and i decided to replace it. I actually bought two drives,
thinking I'd keep one as a cold spare, but when i got to replacing the drive
(after days of load testing to see if I'd gotten a dud), I figured maybe I'd
use the spare as a hot spare, or make a Raid6 array. In the end I decided on a
Raid6, as it is the recommended way to go these days for large disks.
When I did the add for the first disk, it started rebuilding the raid5, and
said it'd only take like 5 hours, then I added the second disk and it
skyrocketed to about 116 hours (7000s or so). I presume this is expected, due
to having to re-stripe all of the data, and re-calculate the parity at the
same time.
How much faster would this have finished if I had just waited for the first
drive to finish rebuilding and done the reshape as a separate step? I decided
to just let this reshape continue, its about 30% the way through, and this is
actually the backup array for my main NAS, so it isn't actually a problem if
it dies mid-reshape. I'm just curious about the alternatives to how I did it.
I know i could have just copied the old disk to one of the new ones, and
skipped the entire rebuild on one disk, but i didn't feel like it ;D
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next reply other threads:[~2015-04-17 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 17:55 Thomas Fjellstrom [this message]
2015-04-18 13:13 ` Raid 5 rebuild and Raid 6 reshape question Mikael Abrahamsson
2015-04-18 19:38 ` Thomas Fjellstrom
2015-04-19 8:43 ` Mikael Abrahamsson
2015-04-19 19:42 ` Thomas Fjellstrom
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=6744821.j7csV3RJVE@balsa \
--to=thomas@fjellstrom.ca \
--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).