Bug 1034013

Summary: xfstests xfs/300: xfs_fsr / swapext management test failed
Product: Red Hat Enterprise Linux 7 Reporter: Eryu Guan <eguan>
Component: xfsprogsAssignee: Eric Sandeen <esandeen>
Status: CLOSED CURRENTRELEASE QA Contact: Boris Ranto <branto>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: branto
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: xfsprogs-3.2.0-0.3.alpha2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 11:45:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Full test log none

Description Eryu Guan 2013-11-25 04:29:39 UTC
Created attachment 828510 [details]
Full test log

Description of problem:
Seems a known issue in upstream, file one bug to track it internally.

=== full diff out/out.bad ===
--- /dev/fd/63	2013-11-15 09:09:05.644743927 -0500
+++ results/xfs/300.out.bad	2013-11-15 09:09:03.489861105 -0500
@@ -1,3 +1 @@
 QA output created by 300
-SCRATCH_MNT/300.test
-extents before:6 after:1 DONE SCRATCH_MNT/300.test

Version-Release number of selected component (if applicable):
xfsprogs-3.2.0-0.1.alpha1.el7

How reproducible:
always

Steps to Reproduce:
1. check xfs/300 on xfs
2.
3.

Actual results:
test fails

Expected results:
test passes

Additional info:

Comment 1 Eric Sandeen 2013-11-25 16:18:50 UTC
Fixed upstream, will be in 3.2.0-alpha2 soon.

Comment 2 Eric Sandeen 2014-02-21 18:38:56 UTC
Hm, on my box now it's doing:

 QA output created by 300
 SCRATCH_MNT/300.test
-extents before:6 after:1 DONE SCRATCH_MNT/300.test
+extents before:7 after:1 DONE SCRATCH_MNT/300.test

which is a different "problem" - original file created w/ more extents than expected.

Comment 3 Eric Sandeen 2014-02-21 18:42:33 UTC
Ok, it's just a test bug now that the actual underlying bug is fixed.

It's doing:

# Fragment the file by writing backwards
for I in `seq 6 -1 0`; do
        dd if=/dev/zero of=$SCRATCH_MNT/$seq.test seek=$I bs=4k \
           oflag=direct count=1 conv=notrunc >> $seqres.full 2>&1
done

and we're getting:

 EXT: FILE-OFFSET      BLOCK-RANGE      AG AG-OFFSET        TOTAL
   0: [0..7]:          160..167          0 (160..167)           8
   1: [8..15]:         152..159          0 (152..159)           8
   2: [16..23]:        144..151          0 (144..151)           8
   3: [24..31]:        136..143          0 (136..143)           8
   4: [32..39]:        128..135          0 (128..135)           8
   5: [40..47]:        120..127          0 (120..127)           8
   6: [48..55]:        112..119          0 (112..119)           8

As expected.  ;)  The .out file is simply wrong, I'll send a patch upstream.

Comment 6 Ludek Smid 2014-06-13 11:45:12 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.