From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-ext4@vger.kernel.org
Subject: Re: e2scrub finds corruption immediately after mounting
Date: Tue, 16 Jan 2024 08:22:07 -0500 [thread overview]
Message-ID: <41b3d30367b59f6dfd96181e3b3052720127b98f.camel@interlinx.bc.ca> (raw)
In-Reply-To: <20240110180614.GE722946@frogsfrogsfrogs>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Wed, 2024-01-10 at 10:06 -0800, Darrick J. Wong wrote:
>
> Huh. Do you remember the exact command that was used to format this
> filesystem?
I do not. It was created quite a while ago.
> "mke2fs" still formats ext2 filesystems unless you pass
> -T ext4 or call its cousin mkfs.ext4.
I wonder if that's what I did perhaps.
> Nope. ext4 is really just ext2 plus a bunch of new features
> (journal,
> extents, uninit_bg, dir_index).
Yes, that's completely understood. I would have thought it an
interesting "safety" measure to flag that when a user requests an ext4
mount and the file system is actually only ext2 that a refusal to mount
would indicate to the user that their ext* file system does not have
the required features to be called ext4.
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-16 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 21:14 e2scrub finds corruption immediately after mounting Brian J. Murrell
2024-01-04 4:38 ` Theodore Ts'o
2024-01-04 14:10 ` Brian J. Murrell
2024-01-04 4:55 ` Darrick J. Wong
2024-01-04 14:13 ` Brian J. Murrell
2024-01-08 12:52 ` Brian J. Murrell
2024-01-09 6:06 ` Darrick J. Wong
2024-01-10 5:31 ` Darrick J. Wong
2024-01-10 13:44 ` Brian J. Murrell
2024-01-10 18:06 ` Darrick J. Wong
2024-01-10 23:43 ` Andreas Dilger
2024-01-16 13:29 ` Brian J. Murrell
2024-01-16 13:22 ` Brian J. Murrell [this message]
2024-01-17 19:42 ` Andreas Dilger
2024-01-17 22:20 ` Brian J. Murrell
2024-01-04 14:37 ` Brian J. Murrell
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=41b3d30367b59f6dfd96181e3b3052720127b98f.camel@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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 NNTP newsgroup(s).