shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity
c98617c593
lvm2/test/shell/lvresize-rounding.sh

93 lines
2.1 KiB
Bash
Raw Normal View History

tests: use bash
2017-07-02 22:38:32 +03:00
#!/usr/bin/env bash
Update test
2012-04-11 16:53:46 +04:00
# Copyright (C) 2007-2012 Red Hat, Inc. All rights reserved.
When resizing LVs, always round in the safe direction, regardless of whether we were called as lvresize or lvreduce.
2011-09-15 22:51:11 +04:00
#
# 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
When resizing LVs, always round in the safe direction, regardless of whether we were called as lvresize or lvreduce.
2011-09-15 22:51:11 +04:00
tests: enable lvmlockd for passing tests
2018-05-24 17:49:48 +03:00
tests: use more SKIP Speed-up check_lvmpolld.
2015-10-27 17:10:06 +03:00
SKIP_WITH_LVMPOLLD=1
When resizing LVs, always round in the safe direction, regardless of whether we were called as lvresize or lvreduce.
2011-09-15 22:51:11 +04:00
tests: use more SKIP Speed-up check_lvmpolld.
2015-10-27 17:10:06 +03:00
. lib/inittest
lvmpolld: Add standalone polldaemon. See doc/lvmpolld_overview.txt
2015-05-09 02:59:18 +03:00
Update test
2012-04-11 16:53:46 +04:00
aux prepare_pvs 3 22
tests: replace cat usage
2017-07-06 20:41:25 +03:00
get_devs
When resizing LVs, always round in the safe direction, regardless of whether we were called as lvresize or lvreduce.
2011-09-15 22:51:11 +04:00
tests: enable lvmlockd for passing tests
2018-05-24 17:49:48 +03:00
vgcreate $SHARED -s 32K "$vg" "${DEVICES[@]}"
When resizing LVs, always round in the safe direction, regardless of whether we were called as lvresize or lvreduce.
2011-09-15 22:51:11 +04:00
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l4 -i3 -I64 $vg
When resizing LVs, always round in the safe direction, regardless of whether we were called as lvresize or lvreduce.
2011-09-15 22:51:11 +04:00
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l8 -i2 -I64 $vg
Update test
2012-04-11 16:53:46 +04:00
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l16 $vg
Update test
2012-04-11 16:53:46 +04:00
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l32 -i3 -I64 -n $lv1 $vg
Update test
2012-04-11 16:53:46 +04:00
lvresize -l+64 -i3 -I64 $vg/$lv1
lvresize -l+64 -i3 -I128 $vg/$lv1
#lvcreate -l100%FREE -i3 -I64 --alloc anywhere $vg
vgremove -f $vg
# 15 extents
tests: temporarily trace prepare_vg
2015-03-26 17:05:24 +03:00
LVM_TEST_AUX_TRACE=yes
Update test
2012-04-11 16:53:46 +04:00
aux prepare_vg 3 22
tests: temporarily trace prepare_vg
2015-03-26 17:05:24 +03:00
unset LVM_TEST_AUX_TRACE
Update test
2012-04-11 16:53:46 +04:00
# Block some extents
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l4 -i3 $vg
lvcreate -an -Zn -l1 $vg
Update test
2012-04-11 16:53:46 +04:00
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l100%FREE -n $lv1 -i3 $vg
Update test
2012-04-11 16:53:46 +04:00
check vg_field $vg vg_free_count 2
lvremove -f $vg/$lv1
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l1 -n $lv1 -i3 $vg
Update test
2012-04-11 16:53:46 +04:00
lvextend -l+100%FREE -i3 $vg/$lv1
check vg_field $vg vg_free_count 2
lvresize: add new options and defaults for fs handling The new option "--fs String" for lvresize/lvreduce/lvextend controls the handling of file systems before/after resizing the LV. --resizefs is the same as --fs resize. The new option "--fsmode String" can be used to control mounting and unmounting of the fs during resizing. Possible --fs values: checksize Only applies to reducing size; does nothing for extend. Check the fs size and reduce the LV if the fs is not using the affected space, i.e. the fs does not need to be shrunk. Fail the command without reducing the fs or LV if the fs is using the affected space. resize Resize the fs using the fs-specific resize command. This may include mounting, unmounting, or running fsck. See --fsmode to control mounting behavior, and --nofsck to disable fsck. resize_fsadm Use the old method of calling fsadm to handle the fs (deprecated.) Warning: this option does not prevent lvreduce from destroying file systems that are unmounted (or mounted if prompts are skipped.) ignore Resize the LV without checking for or handling a file system. Warning: using ignore when reducing the LV size may destroy the file system. Possible --fsmode values: manage Mount or unmount the fs as needed to resize the fs, and attempt to restore the original mount state at the end. nochange Do not mount or unmount the fs. If mounting or unmounting is required to resize the fs, then do not resize the fs or the LV and fail the command. offline Unmount the fs if it is mounted, and resize the fs while it is unmounted. If mounting is required to resize the fs, then do not resize the fs or the LV and fail the command. Notes on lvreduce: When no --fs or --resizefs option is specified: . lvextend default behavior is fs ignore. . lvreduce default behavior is fs checksize (includes activating the LV.) With the exception of --fs resize_fsadm|ignore, lvreduce requires the recent libblkid fields FSLASTBLOCK and FSBLOCKSIZE. FSLASTBLOCK*FSBLOCKSIZE is the last byte used by the fs on the LV, which determines if reducing the fs is necessary.
2022-06-14 23:20:21 +03:00
lvreduce -f --fs ignore -l50%LV $vg/$lv1
Update test
2012-04-11 16:53:46 +04:00
vgremove -f $vg
tests: enable lvmlockd for passing tests
2018-05-24 17:49:48 +03:00
vgcreate $SHARED -s 4M $vg "$dev1" "$dev2" "$dev3"
Update test
2012-04-11 16:53:46 +04:00
# Expect to play with 15 extents
check vg_field $vg vg_free_count 15
# Should be rounded to 12 extents
tests: more test run in cluster mode aux updates: prepare_vg now created clustered VG for cluster tests. since dm-raid doesn't work in cluster, skip the cluster test when someone checks for dm-raid target until fixed.
2013-06-15 13:21:03 +04:00
lvcreate -an -Zn -l10 -n lv -i3 $vg
Update test
2012-04-11 16:53:46 +04:00
check vg_field $vg vg_free_count 3
# Should want 16 extents
not lvextend -l+4 $vg/lv
# Round up to whole free space
lvextend -l+100%FREE $vg/lv
check vg_field $vg vg_free_count 0
# Rounds up and should reduce just by 3 extents
lvresize: add new options and defaults for fs handling The new option "--fs String" for lvresize/lvreduce/lvextend controls the handling of file systems before/after resizing the LV. --resizefs is the same as --fs resize. The new option "--fsmode String" can be used to control mounting and unmounting of the fs during resizing. Possible --fs values: checksize Only applies to reducing size; does nothing for extend. Check the fs size and reduce the LV if the fs is not using the affected space, i.e. the fs does not need to be shrunk. Fail the command without reducing the fs or LV if the fs is using the affected space. resize Resize the fs using the fs-specific resize command. This may include mounting, unmounting, or running fsck. See --fsmode to control mounting behavior, and --nofsck to disable fsck. resize_fsadm Use the old method of calling fsadm to handle the fs (deprecated.) Warning: this option does not prevent lvreduce from destroying file systems that are unmounted (or mounted if prompts are skipped.) ignore Resize the LV without checking for or handling a file system. Warning: using ignore when reducing the LV size may destroy the file system. Possible --fsmode values: manage Mount or unmount the fs as needed to resize the fs, and attempt to restore the original mount state at the end. nochange Do not mount or unmount the fs. If mounting or unmounting is required to resize the fs, then do not resize the fs or the LV and fail the command. offline Unmount the fs if it is mounted, and resize the fs while it is unmounted. If mounting is required to resize the fs, then do not resize the fs or the LV and fail the command. Notes on lvreduce: When no --fs or --resizefs option is specified: . lvextend default behavior is fs ignore. . lvreduce default behavior is fs checksize (includes activating the LV.) With the exception of --fs resize_fsadm|ignore, lvreduce requires the recent libblkid fields FSLASTBLOCK and FSBLOCKSIZE. FSLASTBLOCK*FSBLOCKSIZE is the last byte used by the fs on the LV, which determines if reducing the fs is necessary.
2022-06-14 23:20:21 +03:00
lvreduce -f --fs ignore -l-4 $vg/lv
Update test
2012-04-11 16:53:46 +04:00
check vg_field $vg vg_free_count 3
# Should round up to 15 extents
lvextend -f -l+1 $vg/lv
check vg_field $vg vg_free_count 0
lvresize: add new options and defaults for fs handling The new option "--fs String" for lvresize/lvreduce/lvextend controls the handling of file systems before/after resizing the LV. --resizefs is the same as --fs resize. The new option "--fsmode String" can be used to control mounting and unmounting of the fs during resizing. Possible --fs values: checksize Only applies to reducing size; does nothing for extend. Check the fs size and reduce the LV if the fs is not using the affected space, i.e. the fs does not need to be shrunk. Fail the command without reducing the fs or LV if the fs is using the affected space. resize Resize the fs using the fs-specific resize command. This may include mounting, unmounting, or running fsck. See --fsmode to control mounting behavior, and --nofsck to disable fsck. resize_fsadm Use the old method of calling fsadm to handle the fs (deprecated.) Warning: this option does not prevent lvreduce from destroying file systems that are unmounted (or mounted if prompts are skipped.) ignore Resize the LV without checking for or handling a file system. Warning: using ignore when reducing the LV size may destroy the file system. Possible --fsmode values: manage Mount or unmount the fs as needed to resize the fs, and attempt to restore the original mount state at the end. nochange Do not mount or unmount the fs. If mounting or unmounting is required to resize the fs, then do not resize the fs or the LV and fail the command. offline Unmount the fs if it is mounted, and resize the fs while it is unmounted. If mounting is required to resize the fs, then do not resize the fs or the LV and fail the command. Notes on lvreduce: When no --fs or --resizefs option is specified: . lvextend default behavior is fs ignore. . lvreduce default behavior is fs checksize (includes activating the LV.) With the exception of --fs resize_fsadm|ignore, lvreduce requires the recent libblkid fields FSLASTBLOCK and FSBLOCKSIZE. FSLASTBLOCK*FSBLOCKSIZE is the last byte used by the fs on the LV, which determines if reducing the fs is necessary.
2022-06-14 23:20:21 +03:00
lvreduce -f --fs ignore -l-4 $vg/lv
Update test
2012-04-11 16:53:46 +04:00
check vg_field $vg vg_free_count 3
lvextend -l90%VG $vg/lv
check vg_field $vg vg_free_count 0
lvresize: add new options and defaults for fs handling The new option "--fs String" for lvresize/lvreduce/lvextend controls the handling of file systems before/after resizing the LV. --resizefs is the same as --fs resize. The new option "--fsmode String" can be used to control mounting and unmounting of the fs during resizing. Possible --fs values: checksize Only applies to reducing size; does nothing for extend. Check the fs size and reduce the LV if the fs is not using the affected space, i.e. the fs does not need to be shrunk. Fail the command without reducing the fs or LV if the fs is using the affected space. resize Resize the fs using the fs-specific resize command. This may include mounting, unmounting, or running fsck. See --fsmode to control mounting behavior, and --nofsck to disable fsck. resize_fsadm Use the old method of calling fsadm to handle the fs (deprecated.) Warning: this option does not prevent lvreduce from destroying file systems that are unmounted (or mounted if prompts are skipped.) ignore Resize the LV without checking for or handling a file system. Warning: using ignore when reducing the LV size may destroy the file system. Possible --fsmode values: manage Mount or unmount the fs as needed to resize the fs, and attempt to restore the original mount state at the end. nochange Do not mount or unmount the fs. If mounting or unmounting is required to resize the fs, then do not resize the fs or the LV and fail the command. offline Unmount the fs if it is mounted, and resize the fs while it is unmounted. If mounting is required to resize the fs, then do not resize the fs or the LV and fail the command. Notes on lvreduce: When no --fs or --resizefs option is specified: . lvextend default behavior is fs ignore. . lvreduce default behavior is fs checksize (includes activating the LV.) With the exception of --fs resize_fsadm|ignore, lvreduce requires the recent libblkid fields FSLASTBLOCK and FSBLOCKSIZE. FSLASTBLOCK*FSBLOCKSIZE is the last byte used by the fs on the LV, which determines if reducing the fs is necessary.
2022-06-14 23:20:21 +03:00
not lvreduce -f --fs ignore -l-10%LV $vg/lv
Update test
2012-04-11 16:53:46 +04:00
check vg_field $vg vg_free_count 0
lvresize: add new options and defaults for fs handling The new option "--fs String" for lvresize/lvreduce/lvextend controls the handling of file systems before/after resizing the LV. --resizefs is the same as --fs resize. The new option "--fsmode String" can be used to control mounting and unmounting of the fs during resizing. Possible --fs values: checksize Only applies to reducing size; does nothing for extend. Check the fs size and reduce the LV if the fs is not using the affected space, i.e. the fs does not need to be shrunk. Fail the command without reducing the fs or LV if the fs is using the affected space. resize Resize the fs using the fs-specific resize command. This may include mounting, unmounting, or running fsck. See --fsmode to control mounting behavior, and --nofsck to disable fsck. resize_fsadm Use the old method of calling fsadm to handle the fs (deprecated.) Warning: this option does not prevent lvreduce from destroying file systems that are unmounted (or mounted if prompts are skipped.) ignore Resize the LV without checking for or handling a file system. Warning: using ignore when reducing the LV size may destroy the file system. Possible --fsmode values: manage Mount or unmount the fs as needed to resize the fs, and attempt to restore the original mount state at the end. nochange Do not mount or unmount the fs. If mounting or unmounting is required to resize the fs, then do not resize the fs or the LV and fail the command. offline Unmount the fs if it is mounted, and resize the fs while it is unmounted. If mounting is required to resize the fs, then do not resize the fs or the LV and fail the command. Notes on lvreduce: When no --fs or --resizefs option is specified: . lvextend default behavior is fs ignore. . lvreduce default behavior is fs checksize (includes activating the LV.) With the exception of --fs resize_fsadm|ignore, lvreduce requires the recent libblkid fields FSLASTBLOCK and FSBLOCKSIZE. FSLASTBLOCK*FSBLOCKSIZE is the last byte used by the fs on the LV, which determines if reducing the fs is necessary.
2022-06-14 23:20:21 +03:00
lvreduce -f --fs ignore -l-20%LV $vg/lv
Update test
2012-04-11 16:53:46 +04:00
check vg_field $vg vg_free_count 3
Copy Permalink