From: Oliver Schinagl <oliver+list@schinagl.nl>
To: linux-raid@vger.kernel.org
Subject: Expanding array with multiple devices
Date: Thu, 28 Feb 2013 21:27:15 +0100 [thread overview]
Message-ID: <512FBDA3.7080501@schinagl.nl> (raw)
Hello list,
I've looked online a bit, but didn't really find the answer to the
following question.
While expanding an existing raid is as simple as mdadm --add, followed
by an mdadm --grow, How would you go about this when expanding it with
multiple devices.
A little bit of background. I have 8 2TB disks, 4 in a current raid5
array, which will be the donor disks en 4 'new' disk going to form the
basis of a new array. I want to change chunk size and re-format to ext4
to a) optimize the new array according to the new parameters
(stride,stripe-width) and (possibly) a new ondisk ext4 disk format (new
features added since last time). The old array was 4 disk raid5, the new
array will be 8 disk raid6.
So far, I have created a new raid6 array with the 4 'new' disks + 2
'missing' for the parity. I have done it this way, so that I would have
enough space to copy (and verify) files. having done a 4 disk raid6
without any missing devices, there would simply have not been enough
space. True I could have used 3 data disks, 1 parity and 1 missing.
Anyway, my plan next, is to expand the array. I can think of the
following options.
a) Remove 1 disk at a time from the old array, and add it to the new
array, first 2 disks would be parity, after that --growing the last two.
Big disadvantage is of course that there will be almost a week or two of
re-syncing going on.
b) Would be to somehow add all 'extra' disks at once, and have it rsync
it all in one go.
Any idea's how best to expand all this?
Oliver
next reply other threads:[~2013-02-28 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:27 Oliver Schinagl [this message]
2013-03-01 6:52 ` Expanding array with multiple devices Mikael Abrahamsson
2013-03-02 11:52 ` Oliver Schinagl
2013-03-02 14:07 ` Roy Sigurd Karlsbakk
2013-03-02 17:11 ` Phil Turmel
2013-03-02 17:15 ` Roy Sigurd Karlsbakk
2013-03-02 17:22 ` Phil Turmel
2013-03-02 17:31 ` Mikael Abrahamsson
2013-03-02 19:14 ` Roy Sigurd Karlsbakk
2013-03-03 3:22 ` Mikael Abrahamsson
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=512FBDA3.7080501@schinagl.nl \
--to=oliver+list@schinagl.nl \
--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.