From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: add large_file to base mkfs features
Date: Wed, 1 Oct 2014 08:34:11 -0400 [thread overview]
Message-ID: <20141001123411.GB2903@thunk.org> (raw)
In-Reply-To: <542B744B.3070602@redhat.com>
On Tue, Sep 30, 2014 at 10:26:03PM -0500, Eric Sandeen wrote:
> large_file (> 2G) support has been around since at least kernel 2.4;
> mkfs of any sufficiently large filesystem sets it "accidentally"
> when the resize inode exceeds 2G. This leaves very small
> filesystems lacking the feature, which potentially changes
> their behavior & codepaths the first time a > 2G file gets
> written.
>
> There's really no reason to be making fresh filesystems which
> strive to keep compatibility with 10 year old kernels; just
> enable large_file at mkfs time. This is particularly obvious
> for ext4 fielsystems, which set huge_file by default, but not
> necessarily large_file.
>
> If old-kernel compatibility is desired, mke2fs.conf can be
> modified locally to remove the feature.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Applied, thanks.
- Ted
prev parent reply other threads:[~2014-10-01 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 3:26 [PATCH] e2fsprogs: add large_file to base mkfs features Eric Sandeen
2014-10-01 4:36 ` Andreas Dilger
2014-10-01 12:34 ` 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=20141001123411.GB2903@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).