]> git.ipfire.org Git - thirdparty/mdadm.git/commitdiff
tests: do not try to 'flushbufs' after stopping a array
authorNeilBrown <neilb@suse.de>
Fri, 10 Jul 2015 04:42:20 +0000 (14:42 +1000)
committerNeilBrown <neilb@suse.de>
Fri, 10 Jul 2015 04:42:20 +0000 (14:42 +1000)
If the array is stopped, there is nothing to flush, and
blockdev can signal an error.

Signed-off-by: NeilBrown <neilb@suse.com>
tests/19raid6auto-repair
tests/19raid6repair
tests/19repair-does-not-destroy

index 23b14e4bb9c33f87615956f595cc4cc92ddaa2a1..7fb1c72f811d650ec1db006002c6dce7858743fc 100644 (file)
@@ -39,5 +39,3 @@ cmp -s -n $array_data_size_in_b $md0 /tmp/RandFile || { echo cmp failed ; exit 2
 
 mdadm -S $md0
 udevadm settle
-blockdev --flushbufs $md0 $devs; sync
-echo 3 > /proc/sys/vm/drop_caches
index a1a91e748105122f86be8f943e14c430c8255943..1159bd3e47c8eefe36b9a2acf47ea89995213d5c 100644 (file)
@@ -42,6 +42,6 @@ for failure in "$dev3 3 3 2" "$dev3 3 2 3" "$dev3 3 2 1" "$dev3 3 2 0" "$dev4 3
 
        mdadm -S $md0
        udevadm settle
-       blockdev --flushbufs $devs; sync
+       sync
        echo 3 > /proc/sys/vm/drop_caches
 done
index 1d3b9b45e20728775211465c7c2387be59914083..a92883fda8ca36a1888f4a5f93767efddbab1fe7 100644 (file)
@@ -26,4 +26,3 @@ cmp -s -n $array_data_size_in_b $md0 /tmp/RandFile || { echo should not mess up
 
 mdadm -S $md0
 udevadm settle
-blockdev --flushbufs $md0 $devs; sync