Hi all,
working on arm (32bit arch), kernel 4.1.6.
Looking to find the reason of a bad result on xfstests,
-tests/generic/009
------------------
i get several "all holes" messages
generic/009 [ 842.949643] run fstests generic/009 at 2015-09-18
15:29:36
- output mismatch (see
/home/angelo/xfstests/results//generic/009.out.bad)
--- tests/generic/009.out 2015-09-17 10:54:06.689071257 +0000
+++ /home/angelo/xfstests/results//generic/009.out.bad 2015-09-18
15:29:41.412784177 +0000
@@ -1,79 +1,45 @@
QA output created by 009
1. into a hole
-0: [0..7]: hole
-1: [8..23]: unwritten
-2: [24..39]: hole
+0: [0..39]: hole
daa100df6e6711906b61c9ab5aa16032
also some other tests are giving the same bad notices.
-tests/generic/308
------------------
I have now: CONFIG_LBDAF=y
In my target device this test creates a 16 Terabytes file 308.tempfile
-rw------- 1 root root 17592186044415 Sep 18 09:40 testfile.308
While "df" is not complaining about:
/dev/mmcblk0p5 8378368 45252 8333116 1% /media/p5
and next rm -f on it hands the cpu to 95%, forever.
This issue seems known from a long time, as it has been discussed in the
thread:
http://oss.sgi.com/archives/xfs/2013-04/msg00273.html
I was wondering if there was any special reason why the Jeff patch has
never been finally applied.
I applied this patch anyway, and tests pass.
Best regards,
Angelo Dureghello
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
