Handling of error paths is problematic when lvm2 starts thin-pool that has mismatching information from what lvm2 knows about thin-pool. This can i.e. happen when user repaired thin-pool after crashes and started thin-pool and tried to create a new thin volume. In such case it might try to create a thinLV with already known device id, and since the message fail - it may further try to even delete such device and as final it will end up with mismatching transaction id. Resulting in messages like this one: device-mapper: message ioctl on (MAJOR:MINOR) failed: File exists Failed to process thin pool message "create_snap 11 4". Failed to suspend thin snapshot origin <VG>/<THIN LV>. Internal error: Writing metadata in critical section. Releasing activation in critical section. libdevmapper exiting with 1 device(s) still suspended.
Improved message - stared with this commit: https://www.redhat.com/archives/lvm-devel/2020-September/msg00152.html https://www.redhat.com/archives/lvm-devel/2020-September/msg00154.html https://www.redhat.com/archives/lvm-devel/2020-September/msg00173.html
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.