From: "Theodore Ts'o" <tytso@mit.edu>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Why isn't ext2 deprecated over ext4?
Date: Thu, 22 Feb 2024 15:12:52 -0500 [thread overview]
Message-ID: <20240222201252.GA744192@mit.edu> (raw)
In-Reply-To: <26213f05-2727-45de-8917-da54430d2d19@thelounge.net>
On Wed, Feb 21, 2024 at 11:57:22PM +0100, Reindl Harald wrote:
>
> Fedora for sure didn't invent the nonsense in "mke2fs.conf" falling back to
> such pervert settings for very small martitions
So first lf all, "very small" means "smaller that 512 megs". The
rationale was to reduce the overhead for small thumb drives, where
maximizing space for data files was considered most important.
In practice, most root file systems tend to be larger than 512 megs.
For example, the absolute minimum EBS size in Amazon's cloud is 1GiB
for General Purpose SSD backed EBS, and 5GiB for HDD backed EBS.
Google Compute Engine's minimum Persistent Disk size is 10 GiB.
In any case, starting in e2fsprogs 1.46.4 (released August 2021, first
shipped in Fedora 36), we changed the default so that 256 byte inodes
is used everywhere, including these small file systems.
If you didn't like the old default, well, for these really small file
systems, the good news is that it's pretty simple to backup, reformat,
and restore the file system. (And of course, when the root file
system is that small, in general reinstalling it is no big deal.)
Cheers,
- Ted
next prev parent reply other threads:[~2024-02-22 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 9:33 Why isn't ext2 deprecated over ext4? Michael Opdenacker
2024-02-21 10:33 ` Reindl Harald
2024-02-21 11:00 ` Jan Kara
2024-02-21 11:39 ` Reindl Harald
2024-02-21 15:48 ` Theodore Ts'o
2024-02-21 22:57 ` Reindl Harald
2024-02-22 20:12 ` Theodore Ts'o [this message]
2024-02-21 16:29 ` Michael Opdenacker
2024-02-21 16:58 ` Jan Kara
2024-02-21 21:11 ` Theodore Ts'o
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=20240222201252.GA744192@mit.edu \
--to=tytso@mit.edu \
--cc=h.reindl@thelounge.net \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).