linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: e2scrub finds corruption immediately after mounting
Date: Wed, 17 Jan 2024 17:20:22 -0500	[thread overview]
Message-ID: <6d9adf5fe060e3d6b5604f895e33a54bd1309d9f.camel@interlinx.bc.ca> (raw)
In-Reply-To: <71B876F0-7E82-4D94-A2C0-DE532E75936B@dilger.ca>

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

On Wed, 2024-01-17 at 12:42 -0700, Andreas Dilger wrote:
> 
> At this stage in the game, it _probably_ makes sense that bare
> "mke2fs"
> default to ext4 instead of ext2 to avoid this issue?

Seems reasonable to me.  :-)

Cheers,
b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-01-17 22:29 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
2024-01-17 19:42                 ` Andreas Dilger
2024-01-17 22:20                   ` Brian J. Murrell [this message]
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=6d9adf5fe060e3d6b5604f895e33a54bd1309d9f.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).