From: Theodore Ts'o <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: "Ryan, Michael" <Michael.Ryan2@lenovoemc.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Please summarize state of ext4 resize >16TB
Date: Wed, 8 Jan 2014 15:04:38 -0500 [thread overview]
Message-ID: <20140108200438.GB17750@thunk.org> (raw)
In-Reply-To: <20140108193018.GF9229@birch.djwong.org>
On Wed, Jan 08, 2014 at 11:30:18AM -0800, Darrick J. Wong wrote:
>
> In most cases it's necessary to turn on 64bit (the feature flag) to cross the
> 16T boundary. I've had patches against resize2fs to add this ability--it
> involves moving data blocks and rewriting group descriptors--on the list for a
> few months, but I don't know of Ted's plans to put them in a release. Probably
> post-1.43, is my guess.
It's something that should eventually hit the master/next branch, so
it should be in an eventual 1.43 release. Of course, I don't
currently have a timeline for when a 1.43 release would come out. :-)
Probably in a few months if I had to guess, though. The 1.42.x
release is pretty much locked down for all but the most trivial new
features, so I will be shortly switching my e2fsprogs focus to testing
and merging in the new features for the 1.43 release.
> I don't have any kernel patches to turn on 64bit, and I haven't any current
> plans to make any.
Turning on 64-bit requires rewriting the block group descriptors, and
searching the inodes to relocate data blocks to make room for the
expanded block group descriptors. As such, I don't expect that we
would ever support on-line enablement of the 64-bit feature. If
you've created a file system without the 64-bit feature, or have a
legacy file system that was created previously, you will have to
unmount the file system in order to set the 64-bit feature.
Regards,
- Ted
prev parent reply other threads:[~2014-01-08 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 19:14 Please summarize state of ext4 resize >16TB Ryan, Michael
2014-01-08 19:30 ` Darrick J. Wong
2014-01-08 20:04 ` Theodore Ts'o [this message]
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=20140108200438.GB17750@thunk.org \
--to=tytso@mit.edu \
--cc=Michael.Ryan2@lenovoemc.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@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 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).