From c1ff85dfb6352424c1f55566dfd50c6bece8d6e4 Mon Sep 17 00:00:00 2001 From: Brian Foster Date: Wed, 18 Jun 2014 09:29:22 +1000 Subject: [PATCH] xfs/013: allow non-write fsstress operations in background workload It has been reported that test xfs/013 probably uses more space than necessary, exhausting space if run against a several GB sized ramdisk. xfs/013 primarily creates, links and removes inodes. Most of the space consumption occurs via the background fsstress workload. Remove the fsstress -w option that suppresses non-write operations. This slightly reduces the storage footprint while still providing a background workload for the test. Signed-off-by: Brian Foster Reviewed-by: Dave Chinner Signed-off-by: Dave Chinner --- tests/xfs/013 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/xfs/013 b/tests/xfs/013 index e95d0271..d47bf53b 100755 --- a/tests/xfs/013 +++ b/tests/xfs/013 @@ -121,7 +121,7 @@ _create $SCRATCH_MNT/dir1 $COUNT _cleaner $SCRATCH_MNT $LOOPS $MINDIRS & # start a background stress workload on the fs -$FSSTRESS_PROG -d $SCRATCH_MNT/fsstress -w -n 9999999 -p 2 -S t \ +$FSSTRESS_PROG -d $SCRATCH_MNT/fsstress -n 9999999 -p 2 -S t \ >> $seqres.full 2>&1 & # Each cycle clones the current directory and makes a random file replacement