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: Thu, 04 Jan 2024 09:10:13 -0500	[thread overview]
Message-ID: <51aa3ceea05945c9f28e884bc2f43a249ef7e23e.camel@interlinx.bc.ca> (raw)
In-Reply-To: <20240104043813.GC108362@mit.edu>

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

On Wed, 2024-01-03 at 23:38 -0500, Theodore Ts'o wrote:
> What distribution are you using,

EL8, specifically AlmaLinux 8.9.

> and what version of the kernel are
> you using?

EL8 is currently shipping 4.18.0-513.9.1.el8_9.x86_64 but as you know
at this point in an EL8 kernel's life, the version hardly reflects
what's actually in the kernel due to the copious backporting RH do
their kernel.

> This error means that e2fsck exited with a non-zero exit status.
> Which is strange because there is no report of any kind of problem
> from e2fsck in its output.

Indeed!  I even added debug output to e2scrub to print e2fsck's exit
value and it's usually 1.

> My best guess is that e2fsck from 1.45.6 is somehow returning a
> non-zero exit status for some reason.  So the first thing I'd suggest
> is upgrading to e2fsprogs 1.47.0 and see if that causes the problem
> to
> resolve itself.

Unfortunately, that doesn't seem to be the solution.  :-(

+ umount /opt
+ e2fsck -y /dev/rootvol_tmp/almalinux8_opt
e2fsck 1.47.0 (5-Feb-2023)
/dev/rootvol_tmp/almalinux8_opt: clean, 1698/178816 files, 482473/716800 blocks
+ e2scrub /dev/rootvol_tmp/almalinux8_opt
  Logical volume "almalinux8_opt.e2scrub" created.
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/rootvol_tmp/almalinux8_opt.e2scrub: 1698/178816 files (87.0% non-contiguous), 482473/716800 blocks
/dev/rootvol_tmp/almalinux8_opt: Scrub succeeded.
tune2fs 1.47.0 (5-Feb-2023)
Setting current mount count to 0
Setting time filesystem last checked to Thu Jan  4 09:07:56 2024

  Logical volume "almalinux8_opt.e2scrub" successfully removed.
+ mount /opt
+ e2scrub /dev/rootvol_tmp/almalinux8_opt
  Logical volume "almalinux8_opt.e2scrub" created.
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/rootvol_tmp/almalinux8_opt.e2scrub: 1698/178816 files (87.0% non-contiguous), 482473/716800 blocks
/dev/rootvol_tmp/almalinux8_opt: Scrub FAILED due to corruption!  Unmount and run e2fsck -y.
tune2fs 1.47.0 (5-Feb-2023)
Setting filesystem error flag to force fsck.
  Logical volume "almalinux8_opt.e2scrub" successfully removed.

Cheers,
b.



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

  reply	other threads:[~2024-01-04 14:10 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 [this message]
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
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=51aa3ceea05945c9f28e884bc2f43a249ef7e23e.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).