From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Ram Ramesh <rramesh2400@gmail.com>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: My MD is too big to resize ext4.
Date: Sat, 8 Jul 2017 08:50:40 +0200 [thread overview]
Message-ID: <20170708065040.GA3682@metamorpher.de> (raw)
In-Reply-To: <6c827d07-19d8-017b-ca95-5e6f84b7821a@gmail.com>
On Fri, Jul 07, 2017 at 07:41:13PM -0500, Ram Ramesh wrote:
> On the web, I only found one solution that required upgrading kernel to
> some very recent one (not in my distro) and getting the bleeding edge
> resize2fs. This makes me nervous. Is there a solution that avoids this.
Well, if that works nowadays, then just go for it (LiveCD).
For details you should ask the ext4 mailing list I guess.
You can assemble your RAID in read-only mode and then use
overlays for a non-destructive test run. To make really extra sure
you could even export it via NBD/KVM to see if the old kernel
is able to mount it.
IIRC, btrfs also has a migration path (ext4 to btrfs converter)
and then you could grow that. But then you're stuck with btrfs.
> My filesystem is on md0 drive so I guess partitioning and making into 2x
> 12TB ext4 will not work. I am not even sure if we can partition md like
> any other disk.
Adding a partition table or LVM header would shift the start position.
So it would involve moving/shifting all your data in-place or using
a conversion to LVM. (We just had that in the thread above yours,
subject "linear device of two arrays")
If your RAID has a large enough data offset, you could shift that
to add some extra space at the start of the RAID, but it has to
be done with great care (must be aligned to whatever your RAID
layout is so data will be intact and not garbled).
All in-place operations are kind of hackish/dangerous.
I actually prefer using several smaller filesystems over one gigantic one.
It's all great until your one and only filesystem goes corrupt.
Regards
Andreas Klauer
next prev parent reply other threads:[~2017-07-08 6:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:41 My MD is too big to resize ext4 Ram Ramesh
2017-07-08 6:50 ` Andreas Klauer [this message]
2017-07-08 18:12 ` Ram Ramesh
2017-07-08 19:44 ` Andreas Klauer
2017-07-08 22:22 ` Ram Ramesh
2017-07-09 23:09 ` Ram Ramesh
2017-07-08 7:34 ` Brad Campbell
2017-07-08 7:40 ` Reindl Harald
2017-07-08 8:12 ` Brad Campbell
2017-07-08 18:19 ` Ram Ramesh
2017-07-08 18:48 ` Ram Ramesh
2017-07-08 8:30 ` Wols Lists
2017-07-08 18:28 ` Ram Ramesh
2017-07-08 11:15 ` Roman Mamedov
2017-07-08 18:37 ` Ram Ramesh
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=20170708065040.GA3682@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--cc=linux-raid@vger.kernel.org \
--cc=rramesh2400@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).