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
..
columns-cmdlog.h	report: add CMDLOG report type	2016-06-20 11:33:08 +02:00
columns-devtypes.h	doc: change fsf address	2016-01-21 12:11:37 +01:00
columns.h	vgs: add report field for shared	2018-05-31 10:23:03 -05:00
properties.c	Merge branch 'master' into 2018-05-11-fork-libdm	2018-06-01 13:04:12 +01:00
properties.h	device_mapper: rename libdevmapper.h -> all.h	2018-06-08 12:31:45 +01:00
report.c	Use "cachevol" to refer to cache on a single LV	2019-02-27 08:52:34 -06:00
report.h	build: Don't generate symlinks in include/ dir	2018-05-14 10:30:20 +01:00
values.h	vgs: add report field for shared	2018-05-31 10:23:03 -05:00