All of lore.kernel.org
 help / color / mirror / Atom feed
From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/test t-vgcreate-usage.sh
Date: 9 Jul 2009 08:50:56 -0000	[thread overview]
Message-ID: <20090709085056.31824.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski at sourceware.org	2009-07-09 08:50:55

Modified files:
	test           : t-vgcreate-usage.sh 

Log message:
	Update t-vgcreate-usage.sh to check for default vg properties.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/test/t-vgcreate-usage.sh.diff?cvsroot=lvm2&r1=1.7&r2=1.8

--- LVM2/test/t-vgcreate-usage.sh	2009/05/08 05:15:52	1.7
+++ LVM2/test/t-vgcreate-usage.sh	2009/07/09 08:50:55	1.8
@@ -69,9 +69,6 @@
 
 # Test default (4MB) vg_extent_size as well as limits of extent_size
 not vgcreate --physicalextentsize 0K $vg $dev1 $dev2
-vgcreate $vg $dev1 $dev2
-check_vg_field_ $vg vg_extent_size 4.00M
-vgremove -ff $vg
 vgcreate --physicalextentsize 1K $vg $dev1 $dev2
 check_vg_field_ $vg vg_extent_size 1.00K
 vgremove -ff $vg
@@ -79,3 +76,11 @@
 not vgcreate --physicalextentsize 1024T $vg $dev1 $dev2
 #not vgcreate --physicalextentsize 1T $vg $dev1 $dev2
 # FIXME: vgcreate allows physicalextentsize larger than pv size!
+
+# Test default max_lv, max_pv, extent_size, alloc_policy, clustered
+vgcreate $vg $dev1 $dev2
+check_vg_field_ $vg vg_extent_size 4.00M
+check_vg_field_ $vg max_lv 0
+check_vg_field_ $vg max_pv 0
+check_vg_field_ $vg vg_attr "wz--n-"
+vgremove -ff $vg



             reply	other threads:[~2009-07-09  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09  8:50 wysochanski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-08  5:15 LVM2/test t-vgcreate-usage.sh wysochanski
2008-08-28 11:09 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=20090709085056.31824.qmail@sourceware.org \
    --to=wysochanski@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.