From 47f623d64b6432fbb3533cb72132c947eeb01941 Mon Sep 17 00:00:00 2001
From: Zdenek Kabelac <zkabelac@redhat.com>
Date: Mon, 21 Sep 2015 22:44:43 +0200
Subject: [PATCH] tests: update removal test

Test is currently checking a very non-standard use case.
Make it a more resistent against being blocked in kernel.
---
 test/shell/snapshot-remove-dmsetup.sh | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/test/shell/snapshot-remove-dmsetup.sh b/test/shell/snapshot-remove-dmsetup.sh
index b5aad1f95..610d3c2df 100644
--- a/test/shell/snapshot-remove-dmsetup.sh
+++ b/test/shell/snapshot-remove-dmsetup.sh
@@ -34,11 +34,19 @@ mkfs.ext2 "$DM_DEV_DIR/$vg1/snap"
 mkdir mnt
 mount -o errors=remount-ro "$DM_DEV_DIR/$vg1/snap" mnt
 
+sync
+
 # intetionally suspend layer bellow
 dmsetup suspend $vg-$lv1
 
 # now this should pass without blocking
-dmsetup suspend --noflush --nolockfs $vg1-snap
+#dmsetup suspend --noflush --nolockfs $vg1-snap &
+dmsetup suspend $vg1-snap &
+
+sleep .5
+
+dmsetup info --noheadings -c -o suspended $vg1-snap | tee out
+should grep -i suspend out
 
 # unlock device below
 dmsetup resume $vg-$lv1