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:37:31 -0500 [thread overview]
Message-ID: <be5e8488f8484194889216603d2aba2812c6adcb.camel@interlinx.bc.ca> (raw)
In-Reply-To: <20240104045540.GD36164@frogsfrogsfrogs>
[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]
As a point of reference, the aforementioned lvcheck doesn't seem to
find any corruption on the same device and here is what it's doing:
…
+ lvcreate -s -L 256M -n almalinux8_opt-lvcheck-temp-20240104 rootvol_tmp/almalinux8_opt
Logical volume "almalinux8_opt-lvcheck-temp-20240104" created.
+ perform_check /dev/rootvol_tmp/almalinux8_opt-lvcheck-temp-20240104 ext2 /tmp/lvcheck.log.e0Xq523Wio
+ local dev=/dev/rootvol_tmp/almalinux8_opt-lvcheck-temp-20240104
+ local fstype=ext2
+ local tmpfile=/tmp/lvcheck.log.e0Xq523Wio
+ case "$fstype" in
+ nice logsave -as /tmp/lvcheck.log.e0Xq523Wio e2fsck -p -C 0 /dev/rootvol_tmp/almalinux8_opt-lvcheck-temp-20240104
/dev/rootvol_tmp/almalinux8_opt-lvcheck-temp-20240104 contains a file system with errors, check forced.
/dev/rootvol_tmp/almalinux8_opt-lvcheck-temp-20240104: 1698/178816 files (87.0% non-contiguous), 482473/716800 blocks
e2fsck exited with status code 1
+ nice logsave -as /tmp/lvcheck.log.e0Xq523Wio e2fsck -fy -C 0 /dev/rootvol_tmp/almalinux8_opt-lvcheck-temp-20240104
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-lvcheck-temp-20240104: 1698/178816 files (87.0% non-contiguous), 482473/716800 blocks
+ return 0
+ log info 'Background scrubbing of /dev/rootvol_tmp/almalinux8_opt succeeded.'
+ local sev=info
+ local 'msg=Background scrubbing of /dev/rootvol_tmp/almalinux8_opt succeeded.'
+ local arg=
+ '[' info == emerg -o info == alert -o info == crit -o info == err -o info == warning ']'
+ logger -t lvcheck -p user.info -- 'Background scrubbing of /dev/rootvol_tmp/almalinux8_opt succeeded.'
+ try_delay_checks /dev/rootvol_tmp/almalinux8_opt ext2
+ local dev=/dev/rootvol_tmp/almalinux8_opt
+ local fstype=ext2
+ case "$fstype" in
+ tune2fs -C 0 -T now /dev/rootvol_tmp/almalinux8_opt
tune2fs 1.47.0 (5-Feb-2023)
Setting current mount count to 0
Setting time filesystem last checked to Thu Jan 4 09:29:25 2024
The significant difference between lvcheck and e2scrub seems to be the
'-E journal_only' option to e2fsck that e2scrub is adding.
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-01-04 14:37 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
2024-01-04 14:37 ` Brian J. Murrell [this message]
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=be5e8488f8484194889216603d2aba2812c6adcb.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).