From: Eryu Guan <eguan@redhat.com>
To: fstests@vger.kernel.org
Cc: Eryu Guan <eguan@redhat.com>
Subject: [PATCH] generic/081: wait for lv to be settled before creating fs on it
Date: Fri, 3 Apr 2015 17:41:15 +0800 [thread overview]
Message-ID: <1428054075-20780-1-git-send-email-eguan@redhat.com> (raw)
Call 'udevadm settle' or 'udevsettle' or 'sleep 1' to make sure new lv
is ready for use before making filesystem on it, depends on which
command is available on the system.
Also sleep 1 before removing the test vg, as the snapshot may block the
test vg from removal for a while.
Signed-off-by: Eryu Guan <eguan@redhat.com>
---
tests/generic/081 | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/tests/generic/081 b/tests/generic/081
index e242c4c..8e1828b 100755
--- a/tests/generic/081
+++ b/tests/generic/081
@@ -36,6 +36,9 @@ _cleanup()
rm -f $tmp.*
# lvm may have umounted it on I/O error, but in case it does not
$UMOUNT_PROG $mnt >/dev/null 2>&1
+ # fsync from xfs_io pins the snapshot in use for a while and blocks
+ # vgremove, sleep 1 to avoid such failure
+ sleep 1
$LVM_PROG vgremove -f $vgname >>$seqres.full 2>&1
$LVM_PROG pvremove -f $SCRATCH_DEV >>$seqres.full 2>&1
}
@@ -62,11 +65,30 @@ snapname=snap_$seq
mnt=$TEST_DIR/mnt_$seq
mkdir -p $mnt
+# use 'udevadm settle' or 'udevsettle' to wait for lv to be settled.
+# newer systems have udevadm command but older systems like RHEL5 don't.
+# But if neither one is available, just set it to "sleep 1" to wait for lv to
+# be settled
+UDEV_SETTLE_PROG="`set_prog_path udevadm`"
+if [ "$UDEV_SETTLE_PROG" == "" ]; then
+ # try udevsettle command
+ UDEV_SETTLE_PROG="`set_prog_path udevsettle`"
+else
+ # udevadm is available, add 'settle' as subcommand
+ UDEV_SETTLE_PROG="$UDEV_SETTLE_PROG settle"
+fi
+# neither command is available, use sleep 1
+if [ "$UDEV_SETTLE_PROG" == "" ]; then
+ UDEV_SETTLE_PROG="sleep 1"
+fi
+
# make sure there's enough disk space for 256M lv, test for 300M here in case
# lvm uses some space for metadata
_scratch_mkfs_sized $((300 * 1024 * 1024)) >>$seqres.full 2>&1
$LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1
$LVM_PROG lvcreate --yes -L 256M -n $lvname $vgname >>$seqres.full 2>&1
+# wait for lv to be settled
+$UDEV_SETTLE_PROG >>$seqres.full 2>&1
# _mkfs_dev exits the test on failure, this can make sure lv is created in
# above vgcreate/lvcreate steps
--
1.8.3.1
next reply other threads:[~2015-04-03 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 9:41 Eryu Guan [this message]
2015-05-04 6:27 ` [PATCH] generic/081: wait for lv to be settled before creating fs on it Dave Chinner
2015-05-06 7:32 ` Eryu Guan
2015-05-06 7:58 ` [PATCH v2] " Eryu Guan
2015-05-06 23:13 ` [PATCH] " Dave Chinner
2015-05-07 3:11 ` Eryu Guan
2015-05-07 3:33 ` [PATCH v3] " Eryu Guan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428054075-20780-1-git-send-email-eguan@redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox