xfs/015: keep create_file running until growfs finished

create_file may run over before growfs, which depends on many reasons. such as
the schedule algorithm, the workload of testing machine, etc. we should always
make sure the create_file run over after growfs, then we can get the valid
result of this test.

Signed-off-by: George Wang <xuw2015@gmail.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>

diff --git a/tests/xfs/015 b/tests/xfs/015
index 4dbf38a2d7c1d4e58acfaf1cd6e54337f2b69b1d..55666a8e34730b2e773f01b588cfbafa0fed6fba 100755 (executable)
--- a/tests/xfs/015
+++ b/tests/xfs/015
@@ -43,9 +43,16 @@ create_file()
 {
        local dir=$1
        local i=0
-
-       while echo -n >$dir/testfile_$i; do
-               let i=$i+1
+       local in_growfs=false
+
+       # keep running until failed after growfs
+       while true; do
+               [ -f $tmp.growfs ] && in_growfs=true
+               while echo -n >$dir/testfile_$i; do
+                       let i=$i+1
+               done
+               $in_growfs && break
+               usleep 1000
        done
 }
 
@@ -89,6 +96,9 @@ echo "Fork $nr_worker workers to consume free inodes in background" >>$seqres.fu
 echo "Grow fs to $((dblocks * 4)) blocks" >>$seqres.full
 $XFS_GROWFS_PROG -D $((dblocks * 4)) $SCRATCH_MNT >>$seqres.full
 
+# mark xfs_growfs finished to create_file
+touch $tmp.growfs
+
 # Wait for background create_file to hit ENOSPC
 wait