From: Wols Lists <antlists@youngman.org.uk>
To: Roman Mamedov <rm@romanrm.net>, Veljko <veljko3@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Linear device of two arrays
Date: Wed, 5 Jul 2017 19:07:22 +0100 [thread overview]
Message-ID: <595D2ADA.8010907@youngman.org.uk> (raw)
In-Reply-To: <20170705214250.0ea99538@natsu>
On 05/07/17 17:42, Roman Mamedov wrote:
> On Wed, 5 Jul 2017 17:34:09 +0200
> Veljko <veljko3@gmail.com> wrote:
>
>> Hello,
>>
>> I have a RAID10 device which I have formated using the mkfs.xfs
>> defaults (Stan helped me with this few years back). I reached 88%
>> capacity and it is time to expand it. I bought 4 more drives to create
>> another RIAD10 array. I would like to create linear device out of
>> those two and grow XFS across the 2nd device. How can this be done
>> without loosing the existing device's data? I would also like to add a
>> spare HDD. Do I have to have a separate spare HDD for each array or
>> one can be used by both of them?
>
> Why make another RAID10? With modern versions of mdadm and kernel you should
> be able to simply reshape the current RAID10 to increase the number of
> devices used from 4 to 8.
>
>
I was thinking of replying, but isn't that not possible for some
versions of RAID-10?
My feeling was, if you can't just add drives to the existing raid 10,
create a new one which you can expand, migrate the fs across (btrfs
would let you do that live, I believe, so xfs probably can too), then
you can scrap the old raid-10 and add the drives into the new one.
Cheers,
Wol
next prev parent reply other threads:[~2017-07-05 18:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 15:34 Linear device of two arrays Veljko
2017-07-05 16:42 ` Roman Mamedov
2017-07-05 18:07 ` Wols Lists [this message]
2017-07-07 11:07 ` Nix
2017-07-07 20:26 ` Veljko
2017-07-07 21:20 ` Andreas Klauer
2017-07-07 21:53 ` Roman Mamedov
2017-07-07 22:20 ` Andreas Klauer
2017-07-07 22:33 ` Andreas Klauer
2017-07-07 22:52 ` Stan Hoeppner
2017-07-08 10:26 ` Veljko
2017-07-08 21:24 ` Stan Hoeppner
2017-07-09 22:37 ` NeilBrown
2017-07-10 11:03 ` Veljko
2017-07-12 10:21 ` Veljko
2017-07-14 2:03 ` NeilBrown
2017-07-14 1:57 ` NeilBrown
2017-07-14 2:05 ` NeilBrown
2017-07-14 13:40 ` Veljko
2017-07-15 0:12 ` NeilBrown
2017-07-17 10:16 ` Veljko
2017-07-18 8:58 ` Veljko
2017-07-20 21:40 ` Veljko
2017-07-20 22:00 ` NeilBrown
2017-07-21 9:15 ` Veljko
2017-07-21 11:37 ` Veljko
2017-07-22 23:03 ` NeilBrown
2017-07-23 10:05 ` Veljko
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=595D2ADA.8010907@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
--cc=veljko3@gmail.com \
/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).