From: Eric Whitney <enwlinux@gmail.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: 6.4-rc2 xfstests-bld nojournal regression - generic/231
Date: Tue, 16 May 2023 13:54:39 -0400 [thread overview]
Message-ID: <ZGPDX3pMMa3yg4yg@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi Ted:
I'm seeing an apparent test regression on 6.4-rc2 while running the nojournal
test case with kvm-xfstests. This is generic/231, which fails with 40%
reliability (or better) for me in 10 trial runs. I'm not seeing failures in
the other test cases, including 0 failures in a 10 trial run on 4k.
The relevant output from 231.full is:
ltp/fsx -q -l 64000000 -o 65536 -N 20000 -S 12221 /vdc/fsx_file1
All 20000 operations completed A-OK!
ltp/fsx -q -l 64000000 -o 65536 -N 20000 -S 30719 /vdc/fsx_file1
ltp/fsx -q -l 64000000 -o 65536 -N 20000 -S 7219 /vdc/fsx_file2
ltp/fsx -q -l 64000000 -o 65536 -N 20000 -S 29252 /vdc/fsx_file3
ltp/fsx -q -l 64000000 -o 65536 -N 20000 -S 7909 /vdc/fsx_file4
All 20000 operations completed A-OK!
All 20000 operations completed A-OK!
All 20000 operations completed A-OK!
All 20000 operations completed A-OK!
ltp/fsx -f -q -l 64000000 -o 65536 -N 20000 -S 6375 /vdc/fsx_file1
All 20000 operations completed A-OK!
_check_generic_filesystem: filesystem on /dev/vdc is inconsistent
*** fsck.ext4 output ***
fsck from util-linux 2.36.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 17 passes checks, but checksum does not match inode. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/vdc: ********** WARNING: Filesystem still has errors **********
This test failure bisects to: a44be64bbecb ("ext4: don't clear SB_RDONLY when
remounting r/w until quota is re-enabled"). Reverting this patch eliminates
the test failure (passes 100/100 trials).
Eric
next reply other threads:[~2023-05-16 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:54 Eric Whitney [this message]
2023-05-27 3:57 ` [PATCH] ext4: enable the lazy init thread when remounting read/write Theodore Ts'o
2023-05-28 17:47 ` Eric Whitney
2023-05-30 19:26 ` Theodore Ts'o
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=ZGPDX3pMMa3yg4yg@debian-BULLSEYE-live-builder-AMD64 \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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