Zdenek Kabelac d6df31fba1 pools: no checking for lv/vgremove deactivation ... Thin-pool and cache-pool targets got already quite stable so let's try to remove checking of pools when using lvremove or vgremove commands. This skips checking pools when they are going to be removed, but it also when removing thin volume that was the only user of a thin-pool. In this case thin-pool will be still there and could be activated again with another thin volume and thin_check will be executed in this moment. In this case it can delay discovery of metadata damage.		2024-04-07 20:44:28 +02:00
..
activate.c	vdo: modprobe dm-vdo for kernels >= 6.9	2024-04-07 20:27:39 +02:00
activate.h	vdo: read live vdo size configuration	2023-01-16 12:37:40 +01:00
dev_manager.c	pools: no checking for lv/vgremove deactivation	2024-04-07 20:44:28 +02:00
dev_manager.h	vdo: read live vdo size configuration	2023-01-16 12:37:40 +01:00
fs.c	cov: avoid using strcpy	2023-02-17 00:00:04 +01:00
fs.h	build: Don't generate symlinks in include/ dir	2018-05-14 10:30:20 +01:00
targets.h	doc: change fsf address	2016-01-21 12:11:37 +01:00