Description of problem: When I open crypt device - and I replace its table line with 'error' target, and I run luksOpen second time - I get 'no error'message telling me what's wrong - just return code is 1 - so something is wrong, but normally I'm not exploring return code - so I'd prefer some error message. Version-Release number of selected component (if applicable): cryptsetup-1.6.8-2.fc24.x86_64 How reproducible: Steps to Reproduce: 1. cryptsetup luksOpen /dev/vg/lvol0 mydev 2. mount /dev/mapper/mydev /mnt/test 3. dmsetup remove --force mydev 4. cryptsetup luksOpen /dev/vg/lvol0 mydev Actual results: return code is 1 no error is printed /me being confused ;) Expected results: telling me, there is something wrong Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
# With recent cryptsetup, this happens # cryptsetup luksOpen /dev/sdb x Enter passphrase for /dev/sdb: Cannot use device x, name is invalid or still in use. Closing as fixed in rawhide.