From: Jan Kara <jack@suse.cz>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: Jan Kara <jack@suse.com>, linux-ext4@vger.kernel.org
Subject: Re: Why isn't ext2 deprecated over ext4?
Date: Wed, 21 Feb 2024 12:00:43 +0100 [thread overview]
Message-ID: <20240221110043.mj4v25a2mtmo54bw@quack3> (raw)
In-Reply-To: <bcaf9066-bb4a-4db3-b423-c9871b6b5a2f@bootlin.com>
Hello,
On Wed 21-02-24 10:33:04, Michael Opdenacker wrote:
> I'm wondering why ext2 isn't marked as deprecated yet as it has 32 bit dates
> and dates will rollover in 2038 (in 14 years from now!).
>
> I'm asking because ext4, when used without a journal, seems to be a worthy
> replacement and has 64 bit dates.
>
> I'll be happy to send a patch to fs/ext2/Kconfig to warn users.
For all practical purposes I agree we expect users to use ext4 driver on a
filesystem without a journal instead of ext2 driver. We are still keeping
ext2 around mostly as a simple reference filesystem for other fs
developers. I agree we should improve the kconfig text to reference users
to ext4.
Regarding y2038 problem - this is really the matter of on-disk format as
created by mke2fs, not so much of the kernel driver. And the kernel will be
warning about that when you mount ext2 so I don't think special handling is
needed for that.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-02-21 11:00 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 [this message]
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
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=20240221110043.mj4v25a2mtmo54bw@quack3 \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=michael.opdenacker@bootlin.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).