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
..
api	Remove python bindings for liblvm2app	2018-06-08 10:33:47 -05:00
dbus	tests/dbus: Re-enable nesting and pvcreate via symlink	2018-12-20 10:27:30 -06:00
lib	tests: aux fix testing for kvdo	2019-01-21 12:53:16 +01:00
shell	Use "cachevol" to refer to cache on a single LV	2019-02-27 08:52:34 -06:00
unit	tests: indent	2018-12-23 01:07:27 +01:00
.gitignore	test: add results/ to .gitignore	2016-12-10 18:00:25 +00:00
Makefile.in	makefiles: ensure test dir can run unit-test	2018-12-01 01:05:53 +01:00