From: Theodore Ts'o <tytso@mit.edu>
To: Michael <mike@draftx.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: EXT4 Larger Than 16TB
Date: Mon, 8 Jul 2013 22:14:03 -0400 [thread overview]
Message-ID: <20130709021403.GC6000@thunk.org> (raw)
In-Reply-To: <CAGJTRcg0SHP3-9V-0nDttZ+atn5Kbhf9RRnn_VOaNOq8MgDe6Q@mail.gmail.com>
On Mon, Jul 08, 2013 at 04:32:50PM -0500, Michael wrote:
> I have a currently 15TB FS that I want to expand to 18TB.
> Unfortunately EXT4 e2fsprogs has an issue that stops you from being
> able to do this:
>
> sudo resize2fs /dev/md0
> resize2fs 1.42.5 (29-Jul-2012)
> resize2fs: New size too large to be expressed in 32 bits
>
> It seems to me, reading the change logs, that this only supported if
> you created your FS with 64 bit specified. There seems to have been a
> patch last year that added support for changing 32->64bit, but I had a
> hard time finding/tracking that.
Unfortuantely, there is no patch that would enable this.
In theory it could be done; it would require doubling the size of the
block group descriptors, which would require moving other metadata
blocks out of the way. Resize2fs does do this when growing a file
system off-line when no blocks are available from the resize inode,
but no one has implemented the necessary changes to extend this to
adding the 64-bit feature.
So it's technically possible, but it's not implemented at this time.
Sorry,
- Ted
next prev parent reply other threads:[~2013-07-09 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 21:32 EXT4 Larger Than 16TB Michael
2013-07-09 2:14 ` Theodore Ts'o [this message]
2013-07-09 13:45 ` Michael
2013-07-21 22:47 ` H. Peter Anvin
2013-07-21 23:43 ` Zheng Liu
2013-07-22 0:44 ` Michael
2013-07-22 0:52 ` Zheng Liu
2013-07-22 0:59 ` Michael
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=20130709021403.GC6000@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mike@draftx.net \
/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).