public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: prajnoha@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2/test/shell inconsistent-metadata.sh unlos ...
Date: Wed, 28 Mar 2012 07:46:00 -0000 [thread overview]
Message-ID: <20120328074638.20351.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: prajnoha@sourceware.org 2012-03-28 07:46:36
Modified files:
test/shell : inconsistent-metadata.sh unlost-pv.sh
Log message:
Fix tests to work with vgscan --cache fixing inconsistent metadata.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/shell/inconsistent-metadata.sh.diff?cvsroot=lvm2&r1=1.3&r2=1.4
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/shell/unlost-pv.sh.diff?cvsroot=lvm2&r1=1.2&r2=1.3
--- LVM2/test/shell/inconsistent-metadata.sh 2012/03/16 13:00:06 1.3
+++ LVM2/test/shell/inconsistent-metadata.sh 2012/03/28 07:46:35 1.4
@@ -32,11 +32,12 @@
grep resized lvs.out | grep 8192
}
-# vgscan fixes up metadata
+# vgscan fixes up metadata (needs --cache option for direct scan if lvmetad is used)
+test -e LOCAL_LVMETAD && cache="--cache"
init
-vgscan 2>&1 | tee cmd.out
+vgscan $cache 2>&1 | tee cmd.out
grep "Inconsistent metadata found for VG $vg" cmd.out
-vgscan 2>&1 | tee cmd.out
+vgscan $cache 2>&1 | tee cmd.out
not grep "Inconsistent metadata found for VG $vg" cmd.out
check
--- LVM2/test/shell/unlost-pv.sh 2012/03/16 13:00:06 1.2
+++ LVM2/test/shell/unlost-pv.sh 2012/03/28 07:46:35 1.3
@@ -12,9 +12,11 @@
. lib/test
check_() {
- vgscan 2>&1 | tee vgscan.out
+ # vgscan needs --cache option for direct scan if lvmetad is used
+ test -e LOCAL_LVMETAD && cache="--cache"
+ vgscan $cache 2>&1 | tee vgscan.out
grep "Inconsistent metadata found for VG $vg" vgscan.out
- vgscan 2>&1 | tee vgscan.out
+ vgscan $cache 2>&1 | tee vgscan.out
not grep "Inconsistent metadata found for VG $vg" vgscan.out
}
reply other threads:[~2012-03-28 7:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120328074638.20351.qmail@sourceware.org \
--to=prajnoha@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).