So this test does lots of fallocate/truncate noise while doing aio overwrites to try and exercise a deadlock found in ext4. Because it runs so hard with ENOSPC it can sometimes cause truncate to fail on btrfs. This is ok and doesn't affect the validity of the test, we just need to catch the output so it doesn't cause the test to fail. Thanks, Signed-off-by: Josef Bacik <jbacik@xxxxxx> --- tests/generic/299 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/generic/299 b/tests/generic/299 index 14cce96..bf02c94 100755 --- a/tests/generic/299 +++ b/tests/generic/299 @@ -130,7 +130,7 @@ _workout() done for ((k=1; k <= NUM_JOBS; k++)) do - truncate -s 0 $SCRATCH_MNT/direct_aio.$k.0 + truncate -s 0 $SCRATCH_MNT/direct_aio.$k.0 >> $seqres.full 2>&1 done # Following like will check that pid is still run. # Once fio exit we can stop fallocate/truncate loop -- 1.8.3.1 _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
