Hi all, I find that "kvm-xfstests -c ext4/1k ext4/049" is failed on
current dev branch because of mkfs.ext4 failure.
I can simply reproduce the failure by:
# kvm-xfstests shell
# /sbin/mkfs.ext4 -F -b 4096 -g 8192 -N 1024 -I 4096 /dev/vdc
mke2fs 1.47.0 (5-Feb-2023)
Discarding device blocks: done
Creating filesystem with 1310720 4k blocks and 1280 inodes
Filesystem UUID: a202296a-c5dd-495c-8aee-4bc92983083a
Superblock backups stored on blocks:
8192, 24576, 40960, 57344, 73728, 204800, 221184, 401408, 663552,
1024000
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
*mkfs.ext4: Inode checksum does not match inode while creating orphan file*
I also try this on my host machine with old version mke2fs. The orphan_file
feature is not set in old version /etc/mke2fs.conf and the mkfs.ext4 works
fine. After orphan_file added to /etc/mke2fs.conf, mkfs.ext4 failed as
following:
# mkfs.ext4 -F -b 4096 -g 8192 -N 1024 -I 4096 /dev/sda1
mke2fs 1.45.6 (20-Mar-2020)
/dev/sda1 contains a ext4 file system
created on Tue Jun 27 03:49:19 2023
Invalid filesystem option set: has_journal,extent,huge_file,
flex_bg,metadata_csum,64bit,dir_nlink,extra_isize,orphan_file
It's likely orphan_file is not supported by old version.
After install new version mke2fs on my host machine. The checksum failure
appears again:
mkfs.ext4 -F -b 4096 -g 8192 -N 1024 -I 4096 /dev/sda1
mke2fs 1.47.0 (5-Feb-2023)
/dev/sda1 contains a ext4 file system
created on Tue Jun 27 03:49:19 2023
Creating filesystem with 1310720 4k blocks and 1280 inodes
Filesystem UUID: 6ea06e27-5d56-4389-afaf-a99055fa85fd
Superblock backups stored on blocks:
8192, 24576, 40960, 57344, 73728, 204800, 221184, 401408, 663552,
1024000
Can anyone help with this?
--
Best wishes
Kemeng Shi
