Public bug reported:

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).

** Affects: ubuntu-power-systems
     Importance: Undecided
         Status: New

** Affects: xfsprogs (Ubuntu)
     Importance: Undecided
     Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
         Status: New


** Tags: architecture-ppc64le bugnameltc-156699 severity-medium 
targetmilestone-inin1710

** Tags added: architecture-ppc64le bugnameltc-156699 severity-medium
targetmilestone-inin1710

** Changed in: ubuntu
     Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => xfsprogs (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704730

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to