7 Commits

Author	SHA1	Message	Date
Zdenek Kabelac	2e9792121f	tests: add have_cache and have_raid ... Need to be aware of build options, when system would be configure without raid or cache support	2014-05-20 21:50:30 +02:00
Zdenek Kabelac	c95d43b28c	tests: update lvcreate-cache	2014-04-01 20:54:10 +02:00
Zdenek Kabelac	47b15b805e	tests: updates ... Add some vgremove calls. Remove uneeded test for some unused commands. Add tests for missing commands.	2014-02-27 13:01:04 +01:00
Zdenek Kabelac	3e49753e6c	tests: cache needs 1.3	2014-02-25 09:36:07 +01:00
Jonathan Brassow	00ce01e52d	cache-pool: Change segtype name from cache_pool to cache-pool ... Thin pools use "thin-pool" for the segment type name. To be consistent, we use "cache-pool" instead of "cache_pool".	2014-02-19 09:26:03 -06:00
Jonathan Brassow	fa4812bf7b	cache: Fix cache LV not being instantiated in kernel ... When an origin exists and the 'lvcreate' command is used to create a cache pool + cache LV, the table is loaded into the kernel but never instantiated (suspend/resume was never called). A user running LVM commands would never know that the kernel did not have the proper state unless they also ran the dmsetup 'table/status' command. The solution is to suspend/resume the cache LV to make the loaded tables become active.	2014-02-14 16:04:31 -06:00
Jonathan Brassow	96626f64fa	cache: Code to allow the create/remove of cache LVs ... This patch allows users to create cache LVs with 'lvcreate'. An origin or a cache pool LV must be created first. Then, while supplying the origin or cache pool to the lvcreate command, the cache can be created. Ex1: Here the cache pool is created first, followed by the origin which will be cached. ~> lvcreate --type cache_pool -L 500M -n cachepool vg /dev/small_n_fast ~> lvcreate --type cache -L 1G -n lv vg/cachepool /dev/large_n_slow Ex2: Here the origin is created first, followed by the cache pool - allowing a cache LV to be created covering the origin. ~> lvcreate -L 1G -n lv vg /dev/large_n_slow ~> lvcreate --type cache -L 500M -n cachepool vg/lv /dev/small_n_fast The code determines which type of LV was supplied (cache pool or origin) by checking its type. It ensures the right argument was given by ensuring that the origin is larger than the cache pool. If the user wants to remove just the cache for an LV. They specify the LV's associated cache pool when removing: ~> lvremove vg/cachepool If the user wishes to remove the origin, but leave the cachepool to be used for another LV, they specify the cache LV. ~> lvremove vg/lv In order to remove it all, specify both LVs. This patch also includes tests to create and remove cache pools and cache LVs.	2014-02-04 16:50:16 -06:00