From: Theodore Ts'o <tytso@mit.edu>
To: Contact <neitsab@ovh.fr>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Make huge files strictly contiguous (fallocate, bigalloc, e4defrag...)
Date: Sun, 20 Apr 2014 16:00:30 -0400 [thread overview]
Message-ID: <20140420200030.GC29727@thunk.org> (raw)
In-Reply-To: <53542236.9030201@ovh.fr>
On Sun, Apr 20, 2014 at 09:38:30PM +0200, Contact wrote:
> > Note that because this uses a new compat feature, "sparse_super2", if
> > you use the new mke2fs to create such a file system, you will also
> > need to make sure the file system is checked using a version of e2fsck
> > that supports this new feature as well. No kernel changes are
> > required to support this, though.
> >
> Any plans to get this feature into master at some point in the
> development?
The maint branch is regularly merged into the master and next
branches, so it's there today. The maint branch will very shortly be
the source of a 1.42.10 maintenance release.
The master branch will eventualy be a 1.43 release; it has some much
more disruptive changes, and adds support for metadata checksums,
inline data, etc. It's likely that 1.42.10 will be the last
maintenance release, and the focus will be on stablizing 1.43 and
making sure we're really ready to support the ABI's for the new
library functions in libext2fs to support these new features _forever_.
Cheers,
- Ted
prev parent reply other threads:[~2014-04-20 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 2:18 Make huge files strictly contiguous (fallocate, bigalloc, e4defrag...) Contact
2014-04-17 12:04 ` Lukáš Czerner
2014-04-17 15:24 ` Theodore Ts'o
2014-04-17 18:41 ` Contact
2014-04-17 20:11 ` Contact
2014-04-18 8:45 ` Lukáš Czerner
2014-04-20 14:37 ` Contact
2014-04-20 19:01 ` Theodore Ts'o
2014-04-20 19:38 ` Contact
2014-04-20 20:00 ` 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=20140420200030.GC29727@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=neitsab@ovh.fr \
/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).