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
