ZTS: Fix removal_cancel.ksh

Create a larger file to extend the time required to perform the
removal.  Occasional failures were observed due to the removal
completing before the cancel could be requested.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: John Kennedy <john.kennedy@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Igor Kozhukhov <igor@dilos.org>
Closes #9259

diff --git a/tests/zfs-tests/tests/functional/removal/removal_cancel.ksh b/tests/zfs-tests/tests/functional/removal/removal_cancel.ksh
index e7fa6abb8bcb1212993a4ccf59918e594a4b4ee4..afb318ef2168db39ea8eacc588225f681ecffaa5 100755 (executable)
--- a/tests/zfs-tests/tests/functional/removal/removal_cancel.ksh
+++ b/tests/zfs-tests/tests/functional/removal/removal_cancel.ksh
@@ -55,11 +55,11 @@ log_must default_setup_noexit "$REMOVEDISK"
 
 #
 # Create a file of size 1GB and then do some random writes.
-# Since randwritecomp does 8K writes we do 12500 writes
-# which means we write ~100MB to the vdev.
+# Since randwritecomp does 8K writes we do 25000 writes
+# which means we write ~200MB to the vdev.
 #
 log_must mkfile -n 1g $SAMPLEFILE
-log_must randwritecomp $SAMPLEFILE 12500
+log_must randwritecomp $SAMPLEFILE 25000
 
 #
 # Add second device where all the data will be evacuated.