From: Roman Mamedov <rm@romanrm.net>
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 16:15:13 +0500 [thread overview]
Message-ID: <20170708161513.37b09dbc@natsu> (raw)
In-Reply-To: <6c827d07-19d8-017b-ca95-5e6f84b7821a@gmail.com>
On Fri, 7 Jul 2017 19:41:13 -0500
Ram Ramesh <rramesh2400@gmail.com> 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.
Considering the other possible options that have been mentioned, using the
Ext4 built-in larger devices support (which has been implemented recently)
seems to be your best bet.
https://askubuntu.com/questions/779754/how-do-i-resize-an-ext4-partition-beyond-the-16tb-limit
The required e2fsprogs version 1.43 is included in Ubuntu 16.10 by now, so you
don't even need to build it from the source.
https://packages.ubuntu.com/yakkety/e2fsprogs
But really, if you have everything on one array with a single huge filesystem
and no backups, that's just asking for trouble and a complete data loss.
--
With respect,
Roman
next prev parent reply other threads:[~2017-07-08 11:15 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
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 [this message]
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=20170708161513.37b09dbc@natsu \
--to=rm@romanrm.net \
--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 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.