xfs
[Top] [All Lists]

[PATCH] xfstests: generic/299 can have truncate fail

To: <linux-btrfs@xxxxxxxxxxxxxxx>, <xfs@xxxxxxxxxxx>
Subject: [PATCH] xfstests: generic/299 can have truncate fail
From: Josef Bacik <jbacik@xxxxxx>
Date: Thu, 30 Jan 2014 17:01:23 -0500
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=from : to : subject : date : message-id : mime-version : content-type; s=facebook; bh=9S9EZ324wHzArbw0xSzDXYq6Vwbch6LGTDlS7H6OcmA=; b=JNLJvB7jGZ411XvrY8u33I1liMDdXXjBcvmZngwvhJEFj0YCm4KJoybATW+G41pHfAES 016MsH46/hkISR9rlJL7pKBPVT4X4AoKSUOjZRNeLRBZT+TeGVNLU7nmSQ0BepBcw+ml CCRMHWxdrEpy+DPt0/K81okfNXJzrP+gGXg=
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

<Prev in Thread] Current Thread [Next in Thread>
  • [PATCH] xfstests: generic/299 can have truncate fail, Josef Bacik <=