tests: flushbufs after writing zeros

sometimes the removed device is re-added before the writes
get all the way to the md device - so the array doesn't need
any recovery and the test fails.
So flush first to be safe.

Signed-off-by: NeilBrown <neilb@suse.com>

diff --git a/tests/05r1-re-add b/tests/05r1-re-add
index 3da1a4a0a113eca6c804cf380ab81cf4070c9541..fa6bbcb421e5421f211241f7f36a75d82a0762bd 100644 (file)
--- a/tests/05r1-re-add
+++ b/tests/05r1-re-add
@@ -30,6 +30,7 @@ cmp --ignore-initial=$[64*512] --bytes=$[$mdsize0*1024] $dev1 $dev2
 mdadm $md0 -f $dev2; sleep 1
 mdadm $md0 -r $dev2
 if dd if=/dev/zero of=$md0 ; then : ; fi
+blockdev --flushbufs $md0 # ensure writes have been sent.
 mdadm $md0 -a $dev2
 check recovery
 check wait

diff --git a/tests/05r1-re-add-nosuper b/tests/05r1-re-add-nosuper
index 8025a6856b77a9c83df234fd62a124f580e03139..058d602d1623c589338299ed7e145ddd9cf7ac31 100644 (file)
--- a/tests/05r1-re-add-nosuper
+++ b/tests/05r1-re-add-nosuper
@@ -29,6 +29,7 @@ cmp --bytes=$[$mdsize0*1024] $dev1 $dev2
 mdadm $md0 -f $dev2; sleep 1
 mdadm $md0 -r $dev2
 if dd if=/dev/zero of=$md0 ; then : ; fi
+blockdev --flushbufs $md0 # make sure writes have been sent
 mdadm $md0 --re-add $dev2
 check recovery
 check wait