Description of problem: Add support for merging a snapshot into it's thinly provisioned origin volume. Will serve as a fundamental command used during system rollback (e.g. after a failed or undesirable upgrade).
Patches are available here, last rebased to lvm2 2.0.99: http://people.redhat.com/msnitzer/patches/upstream/thin-snapshot-merge/series.html (the get_thin_device_id() method needs to be implemented in terms of proper lvm2 code placement)
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Upstream support has been commited - starting with: https://www.redhat.com/archives/lvm-devel/2013-December/msg00017.html Usage: lvconvert --merge vg/thinsnap This will merge thinsnap into its origin device - effectively thinsnap replaces origin and origin is deleted. This works only in the case both volumes could be deactivated. If they are i.e. mounted, merge is deferred to the next activation of merged (origin) LV. While vg/thinsnap is 'merged' and deferred it's not longer accessible for lv commands - so it cannot be deactivated (only volume for deactivation is origin), but its still visible via 'lvs -a' as and invisible volume. For some use-cases see: https://www.redhat.com/archives/lvm-devel/2013-December/msg00026.html