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
..
.exported_symbols	Pre-release cleanups.	2009-05-21 03:04:52 +00:00
file_locking.c	cov: drop uneeded header files	2018-10-15 17:49:44 +02:00
locking_types.h	Implement lock-override options without locking type	2018-06-07 16:17:04 +01:00
locking.c	fix readonly activation override options	2018-09-12 16:30:50 -05:00
locking.h	Remove lvmetad	2018-07-11 11:26:42 -05:00
lvmlockd.c	Use "cachevol" to refer to cache on a single LV	2019-02-27 08:52:34 -06:00
lvmlockd.h	lvmlockd: fix make lockstart wait	2019-01-16 13:24:29 -06:00