linux-ext4 - Re: e2scrub finds corruption immediately after mounting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 16 Jan 2024 08:22:07 -0500
From: "Brian J. Murrell" <brian@...erlinx.bc.ca>
To: linux-ext4@...r.kernel.org
Subject: Re: e2scrub finds corruption immediately after mounting

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.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)