Peter Rajnoha 1e6a926e85 filter: filter-usable: consider snapshot and origin LV as unusable if its component is suspended ... Note that this is just a quick fix and it needs more robust fix to encompass any combination, not just the (old) snapshot one! This started with this report: https://bugzilla.redhat.com/show_bug.cgi?id=1219222 If we have devices/ignore_suspended_devices=1 set based on which we filter out suspended devices as unusable (or if we ignore suspended devices by force, e.g. during lvconvert called from dmeventd) and when we have snapshot and snapshot origin devices in the play, we need to look at their components unerneath (*-real and *-cow) to check if they're not suspended. If they are, the snapshot/snapshot origin is not usable as well and hence it needs to be filtered out by filter-usable.c code which does suspended device filtering. Not going into much details here, more details are in the bugzilla mentioned above. However, this is a quick fix since snapshot and this exact situation is not the only one. So this is something that needs to be revisited and fixed properly with full dm tree and checking the whole stack to state whether the device at the very top is usable or not.		2015-06-17 13:37:53 +02:00
..
activate.c	debug: better tracing messages	2015-06-15 14:48:06 +02:00
activate.h	report: update report_object API	2015-01-20 14:58:43 +01:00
dev_manager.c	filter: filter-usable: consider snapshot and origin LV as unusable if its component is suspended	2015-06-17 13:37:53 +02:00
dev_manager.h	dev_manager: enhance dev_manager_info to acquire LV segment status if requested, add lv_info_with_seg_status fn	2014-11-11 13:04:02 +01:00
fs.c	cleanup: constify activation usage of lv pointer	2014-09-24 10:54:47 +02:00
fs.h	cleanup: constify activation usage of lv pointer	2014-09-24 10:54:47 +02:00
targets.h	Use UUIDs instead of names while processing event handlers.	2010-04-14 13:01:38 +00:00