shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-22 17:35:59 +03:00
Code Releases Activity
447ba5f1c2
lvm2/test/shell/lvrename-cache-thin.sh

53 lines
1.2 KiB
Bash
Raw Normal View History

tests: use bash
2017-07-02 22:38:32 +03:00
#!/usr/bin/env bash
tests: check lvrename of stacked cache pool
2015-12-11 22:11:11 +03:00
# Copyright (C) 2015 Red Hat, Inc. All rights reserved.
#
# This copyrighted material is made available to anyone wishing to use,
# modify, copy, or redistribute it subject to the terms and conditions
# of the GNU General Public License v.2.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software Foundation,
doc: change fsf address Hmm rpmlint suggest fsf is using a different address these days, so lets keep it up-to-date
2016-01-21 13:49:46 +03:00
# Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
tests: check lvrename of stacked cache pool
2015-12-11 22:11:11 +03:00
# Check rename of stacked thin over cached LV
tests: enable lvmlockd for passing tests
2018-05-24 17:49:48 +03:00
tests: check lvrename of stacked cache pool
2015-12-11 22:11:11 +03:00
SKIP_WITH_LVMPOLLD=1
. lib/inittest
aux have_cache 1 3 0 || skip
aux have_thin 1 0 0 || skip
aux prepare_vg 1 80
lvcreate -L10 -n cpool $vg
lvcreate -L10 -n tpool $vg
lvcreate -L10 -n $lv1 $vg
Allow dm-cache cache device to be standard LV If a single, standard LV is specified as the cache, use it directly instead of converting it into a cache-pool object with two separate LVs (for data and metadata). With a single LV as the cache, lvm will use blocks at the beginning for metadata, and the rest for data. Separate dm linear devices are set up to point at the metadata and data areas of the LV. These dm devs are given to the dm-cache target to use. The single LV cache cannot be resized without recreating it. If the --poolmetadata option is used to specify an LV for metadata, then a cache pool will be created (with separate LVs for data and metadata.) Usage: $ lvcreate -n main -L 128M vg /dev/loop0 $ lvcreate -n fast -L 64M vg /dev/loop1 $ lvs -a vg LV VG Attr LSize Type Devices main vg -wi-a----- 128.00m linear /dev/loop0(0) fast vg -wi-a----- 64.00m linear /dev/loop1(0) $ lvconvert --type cache --cachepool fast vg/main $ lvs -a vg LV VG Attr LSize Origin Pool Type Devices [fast] vg Cwi---C--- 64.00m linear /dev/loop1(0) main vg Cwi---C--- 128.00m [main_corig] [fast] cache main_corig(0) [main_corig] vg owi---C--- 128.00m linear /dev/loop0(0) $ lvchange -ay vg/main $ dmsetup ls vg-fast_cdata (253:4) vg-fast_cmeta (253:5) vg-main_corig (253:6) vg-main (253:24) vg-fast (253:3) $ dmsetup table vg-fast_cdata: 0 98304 linear 253:3 32768 vg-fast_cmeta: 0 32768 linear 253:3 0 vg-main_corig: 0 262144 linear 7:0 2048 vg-main: 0 262144 cache 253:5 253:4 253:6 128 2 metadata2 writethrough mq 0 vg-fast: 0 131072 linear 7:1 2048 $ lvchange -an vg/min $ lvconvert --splitcache vg/main $ lvs -a vg LV VG Attr LSize Type Devices fast vg -wi------- 64.00m linear /dev/loop1(0) main vg -wi------- 128.00m linear /dev/loop0(0)
2018-08-17 23:45:52 +03:00
lvconvert --yes --type cache-pool $vg/cpool
tests: check lvrename of stacked cache pool
2015-12-11 22:11:11 +03:00
lvconvert --yes --cache --cachepool cpool $vg/tpool
# currently the only allowed stacking is cache thin data volume
lvconvert --yes --type thin-pool $vg/tpool
lvcreate -V10 $vg/tpool
# check cache pool remains same after thin-pool rename
lvrename $vg/tpool $vg/newpool
check lv_exists $vg newpool cpool
check lv_not_exists $vg tpool
# allowing rename of internal cache pool
lvrename $vg/cpool $vg/cachepool
check lv_exists $vg cachepool
check lv_not_exists $vg cpool
lvs -a $vg
vgremove -f $vg
Copy Permalink