From: mornfall@sourceware.org <mornfall@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/test t-vgsplit-operation.sh
Date: 29 Mar 2010 16:40:51 -0000 [thread overview]
Message-ID: <20100329164051.1015.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mornfall at sourceware.org 2010-03-29 16:40:51
Modified files:
test : t-vgsplit-operation.sh
Log message:
Enforce distinct-PV allocation of snapshot/origin pairs in vgsplit test.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-vgsplit-operation.sh.diff?cvsroot=lvm2&r1=1.24&r2=1.25
--- LVM2/test/t-vgsplit-operation.sh 2009/12/28 18:33:04 1.24
+++ LVM2/test/t-vgsplit-operation.sh 2010/03/29 16:40:51 1.25
@@ -195,8 +195,8 @@
COMM "vgsplit fails splitting one LV with 2 snapshots, only origin LV specified"
vgcreate -c n $vg1 $dev1 $dev2 $dev3 $dev4
lvcreate -l 16 -n $lv1 $vg1 $dev1 $dev2
-lvcreate -l 4 -n $lv2 -s $vg1/$lv1
-lvcreate -l 4 -n $lv3 -s $vg1/$lv1
+lvcreate -l 4 -n $lv2 -s $vg1/$lv1 $dev3
+lvcreate -l 4 -n $lv3 -s $vg1/$lv1 $dev4
vg_validate_pvlv_counts_ $vg1 4 3 2
vgchange -an $vg1
not vgsplit -n $lv1 $vg1 $vg2;
@@ -208,8 +208,8 @@
COMM "vgsplit fails splitting one LV with 2 snapshots, only snapshot LV specified"
vgcreate -c n $vg1 $dev1 $dev2 $dev3 $dev4
lvcreate -l 16 -n $lv1 $vg1 $dev1 $dev2
-lvcreate -l 4 -n $lv2 -s $vg1/$lv1
-lvcreate -l 4 -n $lv3 -s $vg1/$lv1
+lvcreate -l 4 -n $lv2 -s $vg1/$lv1 $dev3
+lvcreate -l 4 -n $lv3 -s $vg1/$lv1 $dev4
vg_validate_pvlv_counts_ $vg1 4 3 2
vgchange -an $vg1
not vgsplit -n $lv2 $vg1 $vg2
next reply other threads:[~2010-03-29 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:40 mornfall [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-30 18:29 LVM2/test t-vgsplit-operation.sh mornfall
2008-09-30 17:56 mornfall
2008-04-10 18:55 wysochanski
2008-04-09 21:10 wysochanski
2008-03-21 21:14 wysochanski
2008-03-04 22:49 wysochanski
2008-02-29 0:09 wysochanski
2008-02-28 17:39 wysochanski
2008-02-28 16:48 wysochanski
2008-01-22 3:30 wysochanski
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=20100329164051.1015.qmail@sourceware.org \
--to=mornfall@sourceware.org \
--cc=lvm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.