14 Commits

Author	SHA1	Message	Date
David Teigland	b869a6ff7a	fix fs block size detection ... blkid_get_tag_value() is not a reliable way to query the fs BLOCK_SIZE, so use the "probe" functions instead.	2022-09-09 15:50:00 -05:00
Zdenek Kabelac	570dbad527	tests: writecache adapt to 300M XFS	2022-09-07 15:00:15 +02:00
David Teigland	a47e20a092	tests: skip tests that require blkid BLOCK_SIZE ... Recent commit 84bd394cf9 "writecache: use block size 4096 when no fs is found" changed the default writecache block size from 512 to 4096 when no file system is detected. The fs block size detection requires the libblkid BLOCK_SIZE feature, so skip tests on systems without this. Otherwise, 4096 writecache added to 512 xfs leads fs io or mount failures.	2021-06-30 11:56:42 -05:00
David Teigland	ff3945777b	tests: enable writecache test that uses cleaner	2020-10-01 11:33:02 -05:00
Zdenek Kabelac	f7c58c636d	tests: use faster awk generator ... Shortens log length.	2020-09-19 17:30:51 +02:00
David Teigland	6ea3654868	tests: writecache tests ... backport updates from later commits	2020-06-10 16:09:36 -05:00
Marian Csontos	e6b93dc24e	test: Fix previous commit	2020-03-18 18:03:12 +01:00
Marian Csontos	fc32787c1b	test: Can not attach writecache to active volume	2020-03-18 14:35:58 +01:00
David Teigland	4829f27b76	writecache: drop real dm suffix ... fixes the problem of adding writecache to an active LV	2020-02-17 13:07:06 -06:00
David Teigland	998e7b1075	writecache: add cvol suffix to attached cachevol ... When an LV is used as a writecache cachevol, give it the LV name a _cvol suffix. Remove the suffix when the cachevol is detached, restoring the original LV name.	2019-10-15 16:03:34 -05:00
David Teigland	a9eaab6beb	Use "cachevol" to refer to cache on a single LV ... and "cachepool" to refer to a cache on a cache pool object. The problem was that the --cachepool option was being used to refer to both a cache pool object, and to a standard LV used for caching. This could be somewhat confusing, and it made it less clear when each kind would be used. By separating them, it's clear when a cachepool or a cachevol should be used. Previously: - lvm would use the cache pool approach when the user passed a cache-pool LV to the --cachepool option. - lvm would use the cache vol approach when the user passed a standard LV in the --cachepool option. Now: - lvm will always use the cache pool approach when the user uses the --cachepool option. - lvm will always use the cache vol approach when the user uses the --cachevol option.	2019-02-27 08:52:34 -06:00
David Teigland	938b6b8253	writecache: prompt before using an LV to hold cache	2019-01-02 11:44:03 -06:00
Zdenek Kabelac	d4de3cfa4d	tests: updates	2018-11-08 12:22:18 +01:00
David Teigland	3ae5569570	Add dm-writecache support ... dm-writecache is used like dm-cache with a standard LV as the cache. $ lvcreate -n main -L 128M -an foo /dev/loop0 $ lvcreate -n fast -L 32M -an foo /dev/pmem0 $ lvconvert --type writecache --cachepool fast foo/main $ lvs -a foo -o+devices LV VG Attr LSize Origin Devices [fast] foo -wi------- 32.00m /dev/pmem0(0) main foo Cwi------- 128.00m [main_wcorig] main_wcorig(0) [main_wcorig] foo -wi------- 128.00m /dev/loop0(0) $ lvchange -ay foo/main $ dmsetup table foo-main_wcorig: 0 262144 linear 7:0 2048 foo-main: 0 262144 writecache p 253:4 253:3 4096 0 foo-fast: 0 65536 linear 259:0 2048 $ lvchange -an foo/main $ lvconvert --splitcache foo/main $ lvs -a foo -o+devices LV VG Attr LSize Devices fast foo -wi------- 32.00m /dev/pmem0(0) main foo -wi------- 128.00m /dev/loop0(0)	2018-11-06 14:18:41 -06:00