public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/test t-pvcreate-operation-md.sh Date: Fri, 28 Jan 2011 16:12:00 -0000 [thread overview] Message-ID: <20110128161247.1277.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-01-28 16:12:46 Modified files: test : t-pvcreate-operation-md.sh Log message: Replacei sleep wait with udev settle Use new udev_wait command instead of unpredictable sleep waiting. As with more devices in the system, udev processing is slower. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-pvcreate-operation-md.sh.diff?cvsroot=lvm2&r1=1.13&r2=1.14 --- LVM2/test/t-pvcreate-operation-md.sh 2011/01/05 01:04:47 1.13 +++ LVM2/test/t-pvcreate-operation-md.sh 2011/01/28 16:12:45 1.14 @@ -34,8 +34,9 @@ cleanup_md() { # sleeps offer hack to defeat: 'md: md127 still in use' # see: https://bugzilla.redhat.com/show_bug.cgi?id=509908#c25 - sleep 2 + aux udev_wait mdadm --stop $mddev || true + aux udev_wait if [ -b "$mddev" ]; then # mdadm doesn't always cleanup the device node sleep 2 @@ -102,6 +103,11 @@ base_mddev_p=`basename $mddev_p_sysfs_name` mddev_p=/dev/${base_mddev_p} + # in case the system is running without devtmpfs /dev + # wait here for created device node on tmpfs + aux udev_wait $mddev_p + test -b $mddev_p || exit 200 + # Checking for 'alignment_offset' in sysfs implies Linux >= 2.6.31 # but reliable alignment_offset support requires kernel.org Linux >= 2.6.33 sysfs_alignment_offset=/sys/dev/block/${mddev_maj_min}/${base_mddev_p}/alignment_offset
next reply other threads:[~2011-01-28 16:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-28 16:12 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-01-05 1:04 mornfall 2011-01-05 0:38 mornfall 2010-08-21 15:43 snitzer 2010-08-12 4:56 snitzer 2010-07-21 14:12 mornfall 2010-05-24 15:28 mornfall 2010-04-13 21:42 wysochanski 2010-01-19 15:59 snitzer 2009-09-13 19:28 mbroz
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=20110128161247.1277.qmail@sourceware.org \ --to=zkabelac@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).