On 5/4/19 1:51 AM, Thomas Huth wrote: >> Hmm, it's passing for me on ext4, but that probably means we have >> different configuration parameters. I'm not sure how to easily show what >> parameters a particular ext4 partition uses to compare the differences >> between your setup and mine (mine is tuned to whatever defaults Fedora's >> installer chose on my behalf), so maybe someone else can chime in. > > $ sudo tune2fs -l /dev/mapper/Home > tune2fs 1.42.9 (28-Dec-2013) > Filesystem volume name: <none> > Last mounted on: /home > Filesystem magic number: 0xEF53 > Filesystem revision #: 1 (dynamic) > Filesystem features: has_journal ext_attr dir_index filetype > needs_recovery meta_bg extent 64bit flex_bg sparse_super large_file > huge_file uninit_bg dir_nlink extra_isize > Filesystem flags: signed_directory_hash > Default mount options: user_xattr acl > Filesystem state: clean > Errors behavior: Continue > Filesystem OS type: Linux > Inode count: 36700160 > Block count: 146800640 > Reserved block count: 5873663 > Free blocks: 56266267 > Free inodes: 35403275 > First block: 1 > Block size: 1024 > Fragment size: 1024 > Group descriptor size: 64 > Blocks per group: 8192 > Fragments per group: 8192 > Inodes per group: 2048 > Inode blocks per group: 256 > First meta block group: 258 > Flex block group size: 16 > Filesystem created: Thu Apr 19 18:34:33 2018 > Last mount time: Sat May 4 08:20:36 2019 > Last write time: Sat May 4 08:20:36 2019 > Mount count: 224 > Maximum mount count: -1 > Last checked: Thu Apr 19 18:34:33 2018 > Check interval: 0 (<none>) > Lifetime writes: 1826 GB > Reserved blocks uid: 0 (user root) > Reserved blocks gid: 0 (group root) > First inode: 11 > Inode size: 128 > Journal inode: 8 > First orphan inode: 11076944 > Default directory hash: half_md4 > Directory Hash Seed: 08e1be04-c3a3-4c37-a059-cf54af5c4bc0 > Journal backup: inode blocks >
# tune2fs -l /dev/mapper/fedora-home tune2fs 1.44.6 (5-Mar-2019) Filesystem volume name: home Last mounted on: /home Filesystem UUID: 3ef45c0b-b2a0-43da-a1d3-c4f726097eda Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 13107200 Block count: 52428800 Reserved block count: 2621440 Free blocks: 27184765 Free inodes: 12049129 First block: 0 Block size: 4096 Fragment size: 4096 Group descriptor size: 64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Thu Dec 6 16:17:23 2018 Last mount time: Wed Apr 3 10:19:05 2019 Last write time: Wed Apr 3 10:19:05 2019 Mount count: 12 Maximum mount count: -1 Last checked: Thu Dec 6 16:17:23 2018 Check interval: 0 (<none>) Lifetime writes: 1962 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 32 Desired extra isize: 32 Journal inode: 8 First orphan inode: 5248434 Default directory hash: half_md4 Directory Hash Seed: d1bbea0e-dd2e-4df7-b7f0-f7300c524cc9 Journal backup: inode blocks Checksum type: crc32c Checksum: 0x3a8a8676 I'm definitely seeing some differences in the two configs (such as your block size of 1k vs. mine at 4k), but not sure which are the most important, nor how to easily recreate a setup that matches yours. > IIRC I talked to stefanha on IRC about this some weeks ago already, and > he was able to reproduce the problem when using a certain parameter to > create the file system. However, I fail to remember which parameter it > was. Maybe Stefan still remembers... > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
