Tests 044, 045, 046 are known to upstream as tests that will currently fail on ext4 as reported back in February 27th, 2017: https://lkml.org/lkml/2017/2/27/674
The upstream maintainer followed up the report with: https://lkml.org/lkml/2017/2/28/4 "On Tue, Feb 28, 2017 at 11:25:56AM +0800, Xiong Zhou wrote: > > On latest Linus tree, xfstests generic/04{4,5,6} fails. Yes, that's known issue. generic/04[456] were originally XFS specific tests, and they have have assumptions about the implementation of the underlying file system. We have a few of those at the moment in kvm-xfstests/gce-xfstests's exclude file: https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/kvm-xfstests /test-appliance/files/root/fs/ext4/exclude # generic/042 and generic/392 are failing because ext4 forces the # resolution of all delayed allocation writes before allowing the # punch operation to proceed. We probably want to see if we can avoid # this for the future, but what ext4 is doing is legal, so just skip # the test for now generic/042 generic/392 # generic/04[456] tests how truncate and delayed allocation works # ext4 uses the data=ordered to avoid exposing stale data, and # so it uses a different mechanism than xfs. So these tests will fail generic/044 generic/045 generic/046 # generic/223 tests file alignment, which works on ext4 only by # accident because we're not RAID stripe aware yet, and works at all # because we have bias towards aligning on power-of-two block numbers. # It is a flaky test for some configurations, so skip it. generic/223 # ext4/304 fails for all configurations, and this appears to be at # test or fio bug. # ext4/304" --- So I think these failures are false positive results for ext4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704730 Title: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 ) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Bug description: xfstests fails non-zero size but no extents on ext4 filesystem Environment ------------------ Kernel Build: 4.12.1-041201-generic Model : 8247-22L Platform : PowerNV ( P8 ) Uname output ------------------- # uname -a Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: ---------------------------------------- 1. Create a loop device with ext4 filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/044 The test 044 fails with following generic/044 - output mismatch (see /root/harish/xfstests-dev/results//generic/044.out.bad) --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400 +++ /root/harish/xfstests-dev/results//generic/044.out.bad 2017-07-14 06:24:08.153731112 -0400 @@ -1 +1,1000 @@ QA output created by 044 +corrupt file /mnt/scratch/1 - non-zero size but no extents +corrupt file /mnt/scratch/2 - non-zero size but no extents +corrupt file /mnt/scratch/3 - non-zero size but no extents +corrupt file /mnt/scratch/4 - non-zero size but no extents +corrupt file /mnt/scratch/5 - non-zero size but no extents +corrupt file /mnt/scratch/6 - non-zero size but no extents ... (Run 'diff -u tests/generic/044.out /root/harish/xfstests-dev/results//generic/044.out.bad' to see the entire diff) Ran: generic/044 Failures: generic/044 Failed 1 of 1 tests Dmesg: ---------- [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49 [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17246.535534] EXT4-fs (loop2): shut down requested (1) [17246.535625] Aborting journal on device loop2-8. [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17259.888304] EXT4-fs (loop2): shut down requested (2) [17259.995751] Aborting journal on device loop2-8. [17260.113582] EXT4-fs (loop2): recovery complete [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr == Comment: #2 - SEETEENA THOUFEEK <sthou...@in.ibm.com> - 2017-07-17 02:10:52 == Issue does not happen when running the same test with xfs file system. (ie, creating loop device with xfs file system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
