From: "Lukáš Czerner" <lczerner@redhat.com>
To: linux-ext4@vger.kernel.org
Subject: Re: [RFC][PATCH] mke2fs.conf: Enable 64bit feature by default
Date: Mon, 3 Mar 2014 16:47:12 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1403031646550.2258@localhost.localdomain> (raw)
In-Reply-To: <1371825747-9031-1-git-send-email-lczerner@redhat.com>
On Fri, 21 Jun 2013, Lukas Czerner wrote:
> Date: Fri, 21 Jun 2013 16:42:27 +0200
> From: Lukas Czerner <lczerner@redhat.com>
> To: linux-ext4@vger.kernel.org
> Cc: Lukas Czerner <lczerner@redhat.com>
> Subject: [RFC][PATCH] mke2fs.conf: Enable 64bit feature by default
Hi Ted,
are you going to take this in ?
Thanks!
-Lukas
>
> The 64bit feature has been added to the ext4 a long time ago (2006?) so
> it should be ok to enable it by default by now. This would allow us to
> resize the file system past 16TB when it was originally smaller than
> that and user did not specified 64bit feature manually.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
> ---
> misc/mke2fs.conf.in | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/misc/mke2fs.conf.in b/misc/mke2fs.conf.in
> index 178733f..dde3219 100644
> --- a/misc/mke2fs.conf.in
> +++ b/misc/mke2fs.conf.in
> @@ -11,8 +11,7 @@
> features = has_journal
> }
> ext4 = {
> - features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
> - auto_64-bit_support = 1
> + features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize,64bit
> inode_size = 256
> }
> ext4dev = {
>
prev parent reply other threads:[~2014-03-03 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 14:42 [RFC][PATCH] mke2fs.conf: Enable 64bit feature by default Lukas Czerner
2014-03-03 15:47 ` Lukáš Czerner [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=alpine.LFD.2.00.1403031646550.2258@localhost.localdomain \
--to=lczerner@redhat.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