linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-ext4@vger.kernel.org
Subject: Re: e2scrub finds corruption immediately after mounting
Date: Mon, 08 Jan 2024 07:52:33 -0500	[thread overview]
Message-ID: <01b2c55a334cf970e49958a5f932d5822bfa74b4.camel@interlinx.bc.ca> (raw)
In-Reply-To: <cf4fb33f3a60629d3b6108c1c206aa5b931d8498.camel@interlinx.bc.ca>

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

On Thu, 2024-01-04 at 09:13 -0500, Brian J. Murrell wrote:
> On Wed, 2024-01-03 at 20:55 -0800, Darrick J. Wong wrote:
> > Curious.  Normally e2scrub will run e2fsck twice: Once in journal-
> > only
> > preen mode to replay the journal, then again with -fy to perform
> > the
> > full filesystem (snapshot) check.
> 
> It is doing that.  I suspect the first e2fsck is silent.
> 
> > I wonder if you would paste the output of
> > "bash -x e2scrub /dev/rootvol_tmp/almalinux8_opt" here?  I'd be
> > curious
> > to see what the command flow is.
> 
> Sure.

Was the bash -x output useful in any way, or was any of the information
I supplied in my other replies on this list:

https://lore.kernel.org/linux-ext4/51aa3ceea05945c9f28e884bc2f43a249ef7e23e.camel@interlinx.bc.ca/
https://lore.kernel.org/linux-ext4/be5e8488f8484194889216603d2aba2812c6adcb.camel@interlinx.bc.ca/

useful including the test of 1.47.0 being able to reproduce the
behaviour?

Any thoughts on how to proceed?

Cheers,
b.


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

  reply	other threads:[~2024-01-08 12:52 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 [this message]
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
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=01b2c55a334cf970e49958a5f932d5822bfa74b4.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).