summaryrefslogtreecommitdiff
path: root/test/shell/lvcreate-thin-big.sh
diff options
context:
space:
mode:
authorZdenek Kabelac <zkabelac@redhat.com>2017-04-08 19:38:17 +0200
committerZdenek Kabelac <zkabelac@redhat.com>2017-04-12 21:34:08 +0200
commit109532290138d3b8b535457150052b6bda4f797c (patch)
tree7ae063e56ba8444c40a00073467691856bbbedf3 /test/shell/lvcreate-thin-big.sh
parent3503ef23e30da87f16b881248be92842a774d7d9 (diff)
downloadlvm2-109532290138d3b8b535457150052b6bda4f797c.tar.gz
thin: properly check for status for max sizes metadata
When metadata LV size was over DM_THIN_MAX_METADATA_SIZE sectors, the info() routine was incorrectly trying to match bigger size, while we do never pass any bigger device. Fixing a case, where lvs should be displaying status for metadata LV with 16GB size.
Diffstat (limited to 'test/shell/lvcreate-thin-big.sh')
-rw-r--r--test/shell/lvcreate-thin-big.sh5
1 files changed, 5 insertions, 0 deletions
diff --git a/test/shell/lvcreate-thin-big.sh b/test/shell/lvcreate-thin-big.sh
index 9abc1fdf9..da7812f4a 100644
--- a/test/shell/lvcreate-thin-big.sh
+++ b/test/shell/lvcreate-thin-big.sh
@@ -37,6 +37,11 @@ lvcreate -L4M --chunksize 64k --poolmetadatasize 17G -T $vg/pool2 2>out
grep "WARNING: Maximum" out
check lv_field $vg/pool1_tmeta size "2.00m"
check lv_field $vg/pool2_tmeta size "16.00g"
+
+# Check can start and see thinpool with metadata size above kernel limit
+lvcreate -L4M --poolmetadatasize 16G -T $vg/poolM
+check lv_field $vg/poolM data_percent "0.00"
+
lvremove -ff $vg
# Test automatic calculation of pool metadata size