public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: mbroz@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/test t-lock-blocking.sh Date: Fri, 04 Mar 2011 15:04:00 -0000 [thread overview] Message-ID: <20110304150409.389.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mbroz@sourceware.org 2011-03-04 15:04:08 Modified files: test : t-lock-blocking.sh Log message: Make the lock test a little bit better... Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-lock-blocking.sh.diff?cvsroot=lvm2&r1=1.5&r2=1.6 --- LVM2/test/t-lock-blocking.sh 2011/03/03 16:04:53 1.5 +++ LVM2/test/t-lock-blocking.sh 2011/03/04 15:04:08 1.6 @@ -21,17 +21,21 @@ # if wait_for_locks set, vgremove should wait for orphan lock # flock process should have exited by the time first vgremove completes flock -w 5 $TESTDIR/var/lock/lvm/P_orphans -c "sleep 10" & -flock_pid=`jobs -p` +while ! test -f $TESTDIR/var/lock/lvm/P_orphans ; do sleep .1 ; done + vgremove --config 'global { wait_for_locks = 1 }' $vg not vgremove --config 'global { wait_for_locks = 1 }' $vg -sleep .2 # leave some time for scheduler to exit flock process -not ps $flock_pid # finished + +test ! -f $TESTDIR/var/lock/lvm/P_orphans # if wait_for_locks not set, vgremove should fail on non-blocking lock # we must wait for flock process at the end - vgremove won't wait vgcreate $vg $dev1 $dev2 flock -w 5 $TESTDIR/var/lock/lvm/P_orphans -c "sleep 10" & + +while ! test -f $TESTDIR/var/lock/lvm/P_orphans ; do sleep .1 ; done flock_pid=`jobs -p` + not vgremove --config 'global { wait_for_locks = 0 }' $vg -ps $flock_pid # still running +test -f $TESTDIR/var/lock/lvm/P_orphans # still running kill $flock_pid
next reply other threads:[~2011-03-04 15:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-04 15:04 mbroz [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-03-03 16:04 zkabelac 2011-01-13 11:05 zkabelac 2010-08-02 13:23 zkabelac 2010-06-24 7:57 mornfall
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=20110304150409.389.qmail@sourceware.org \ --to=mbroz@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).