xfs/013: allow non-write fsstress operations in background workload
authorBrian Foster <bfoster@redhat.com>
Tue, 17 Jun 2014 23:29:22 +0000 (09:29 +1000)
committerDave Chinner <david@fromorbit.com>
Tue, 17 Jun 2014 23:29:22 +0000 (09:29 +1000)
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 <bfoster@redhat.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
tests/xfs/013

index e95d0271f8ee9e819e27d5cbaa87fda93b484522..d47bf53bd40d60cc0bfa7b59175d01b201af2924 100755 (executable)
@@ -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