I can confirm that this bug also occurs in lvm2/2.03.07-1. Essentially,
the merge operation appears to complete successfully, but the snapshot
LV isn't automatically removed. Additionally, the snapshot LV cannot be
manually removed via "lvremove". The workaround I used was to modify the
VG metadata backup (located at /etc/lvm/backup) by removing the snapshot
LV from within the "logical_volumes" section, restoring it via
"vgcfgrestore", and then rebooting.
- Bug#966524: lvm2: lvconvert --merge does not remove the snapshot a... Antonio
- Bug#966524: "lvconvert --merge" does not remove the... ben
