lvm2/test/shell/lvcreate-small-snap.sh

#!/usr/bin/env bash

# Copyright (C) 2010-2014 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,
# Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA


SKIP_WITH_LVMPOLLD=1

. lib/inittest

aux prepare_pvs
get_devs

vgcreate $SHARED -s 4k "$vg" "${DEVICES[@]}"

# 3 Chunks
lvcreate -aey -n one -l 10 $vg
lvcreate -s -l 3 -n snapA $vg/one
lvcreate -s -c 4k -l 3 -n snapX1 $vg/one
lvcreate -s -c 8k -l 6 -n snapX2 $vg/one

# Check that snapshots that are too small are caught with correct error.
not lvcreate -s -c 8k -l 2 -n snapX3 $vg/one 2>&1 | tee lvcreate.out
not grep "suspend origin one" lvcreate.out
grep "smaller" lvcreate.out

not lvcreate -s -l 1 -n snapB $vg/one 2>&1 | tee lvcreate.out
not grep "suspend origin one" lvcreate.out
grep "smaller" lvcreate.out

vgremove -ff $vg
tests: use bash 2017-07-02 22:38:32 +03:00			`#!/usr/bin/env bash`

tests: update error message check 2014-03-17 18:18:02 +04:00			`# Copyright (C) 2010-2014 Red Hat, Inc. All rights reserved.`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +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`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +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`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +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
tests: snapshot needs 3 chunks 2013-05-30 19:55:44 +04:00			`aux prepare_pvs`
tests: replace cat usage 2017-07-06 20:41:25 +03:00			`get_devs`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +04:00
tests: enable lvmlockd for passing tests 2018-05-24 17:49:48 +03:00			`vgcreate $SHARED -s 4k "$vg" "${DEVICES[@]}"`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +04:00
tests: snapshot needs 3 chunks 2013-05-30 19:55:44 +04:00			`# 3 Chunks`
			`lvcreate -aey -n one -l 10 $vg`
tests: happy using of 4K backend devices When the backend device supports only 4K blocks (like ramdisk) we cannot use for testing any smaller blocksize. So recalc test for 4K extent size. We may possibly introduce one list extra test that can be executed on devices with 512b sectors to check lvm2 support those min extent sizes... 2018-05-12 16:58:13 +03:00			`lvcreate -s -l 3 -n snapA $vg/one`
			`lvcreate -s -c 4k -l 3 -n snapX1 $vg/one`
			`lvcreate -s -c 8k -l 6 -n snapX2 $vg/one`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +04:00
			`# Check that snapshots that are too small are caught with correct error.`
tests: happy using of 4K backend devices When the backend device supports only 4K blocks (like ramdisk) we cannot use for testing any smaller blocksize. So recalc test for 4K extent size. We may possibly introduce one list extra test that can be executed on devices with 512b sectors to check lvm2 support those min extent sizes... 2018-05-12 16:58:13 +03:00			`not lvcreate -s -c 8k -l 2 -n snapX3 $vg/one 2>&1 \| tee lvcreate.out`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +04:00			`not grep "suspend origin one" lvcreate.out`
tests: update error message check 2014-03-17 18:18:02 +04:00			`grep "smaller" lvcreate.out`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +04:00
tests: happy using of 4K backend devices When the backend device supports only 4K blocks (like ramdisk) we cannot use for testing any smaller blocksize. So recalc test for 4K extent size. We may possibly introduce one list extra test that can be executed on devices with 512b sectors to check lvm2 support those min extent sizes... 2018-05-12 16:58:13 +03:00			`not lvcreate -s -l 1 -n snapB $vg/one 2>&1 \| tee lvcreate.out`
Give correct error message when creating a too-small snapshot (BZ 587063) 2010-10-13 17:52:53 +04:00			`not grep "suspend origin one" lvcreate.out`
tests: update error message check 2014-03-17 18:18:02 +04:00			`grep "smaller" lvcreate.out`
tests: test should clean devices it has created To be able to detect lvm2 command is not leaking some 'unexpected' device - remove all devices before test exits by its own command so test teardown now can check what was 'left' unexpectedly. 2016-12-11 12:18:44 +03:00
			`vgremove -ff $vg`