xfs
[Top] [All Lists]

[PATCH 6/6] xfs/167: need at least 10GB of scratch space to run

To: xfs@xxxxxxxxxxx
Subject: [PATCH 6/6] xfs/167: need at least 10GB of scratch space to run
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 24 Feb 2014 14:06:15 +1100
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1393211175-30016-1-git-send-email-david@xxxxxxxxxxxxx>
References: <1393211175-30016-1-git-send-email-david@xxxxxxxxxxxxx>
From: Dave Chinner <dchinner@xxxxxxxxxx>

When running on a ramdisk, the fsstress background workload consumes
a GB of disk space every 5 seconds. This leads to the test failing
with ENOSPC because the test file cannot be created due otthe
background load cosuming it all. Hence don't run this test unless
the scratch device is large enough not to hit ENOSPC conditions.

Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
---
 tests/xfs/167 | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/tests/xfs/167 b/tests/xfs/167
index ab0156f..875bd31 100755
--- a/tests/xfs/167
+++ b/tests/xfs/167
@@ -62,6 +62,12 @@ _require_scratch
 _scratch_mkfs_xfs >/dev/null 2>&1
 _scratch_mount
 
+# fast devices can consume disk space at a rate of 1GB every 5s via the
+# background workload. With 50 test loops, at 1 second per loop, that means we
+# need at least 10GB of disk space to ensure this test will not fail with 
ENOSPC
+# errors.
+_require_fs_space $SCRATCH_MNT 10485760
+
 TEST_FILE=$SCRATCH_MNT/test_file
 TEST_PROG=$here/src/unwritten_sync
 LOOPS=50
-- 
1.8.4.rc3

<Prev in Thread] Current Thread [Next in Thread>