Description of problem: When either of the two volumes involved in a snapshot merge are mounted/in use, the merge will be scheduled with the message "Merging of snapshot [snapshot name] will start next activation", but it does not mention upon which volume's activation the merge will start. Even though the snapshot volume will become hidden in lvs, one reason that this is particularly confusing is that it's possible that the entire notification completes with no mention of the origin's name, and the snapshot disappears. Steps to Reproduce: 1. lvcreate -L 1G -n origin vg 2. mkfs.ext4 /dev/mapper/vg-origin 3. lvcreate -s vg/origin -L 1G -n znapshot 4. mkdir /mnt/znapshot 5. mount /dev/mapper/vg-znapshot /mnt/znapshot 6. lvconvert --merge vg/znapshot Actual results: Logical volume vg/znapshot contains a filesystem in use. Can't merge when snapshot is open. Merging of snapshot znapshot will start next activation. Expected results: Logical volume vg/znapshot contains a filesystem in use. Can't merge when snapshot is open. Merging of znapshot will start next activation of origin. Additional info: This change would likely have to be made for thin snapshot merging too.
Already fixed with release of 2.02.112 Tool now reports: Merging of snapshot vg/zsnaphot will occur on next activation of vg/origin.