mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
3bd9f936da
When we have some existing LV and this LV is being converted to external origin - during the DM table manipulation there is a short moment when the LV is being 'resumed' as 'read-only' volume while still being live as 'rw' volume i.e. we could have had a single thin LV active twice. To avoid such weird scenarios of dual access to a same volume, we just postpone a resume until a moment, where the existing volume is already suspended thus no I/O can be in flight to such device. Note: however there is slight catch - that we now have basically a different 'risk' case where a resume of such i.e. new external origin LV might fail and we are already in suspend tree state - resolving error path in this situation is untrivial as well... |
||
|---|---|---|
| .. | ||
| datastruct | ||
| ioctl | ||
| misc | ||
| mm | ||
| regex | ||
| vdo | ||
| all.h | ||
| libdm-common.c | ||
| libdm-common.h | ||
| libdm-config.c | ||
| libdm-deptree.c | ||
| libdm-file.c | ||
| libdm-report.c | ||
| libdm-string.c | ||
| libdm-targets.c | ||
| libdm-timestamp.c | ||
| Makefile | ||