"Cannot read device" on inactive volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Release:
Description: Ubuntu 10.04.4 LTS
Release: 10.04
Version:
cryptsetup:
Installed: 2:1.1.0~
Candidate: 2:1.1.0~
Version table:
*** 2:1.1.0~
500 http://
100 /var/lib/
Scenario:
I have an lvm2 snapshot of an encrypted volume.
I mount the snapshot using cryptsetup.
The available space is exceeded for the snapshot and is left "inactive" by the filesystem.
At this point if I attempt to "luksClose" the crypt device the following error is issued:
"Cannot read device /dev/mapper/
I am unable to destroy the snapshot because it is in use.
Expected Behavior:
I would expect luksClose to have a "force" option where it would close the device even though it cannot read it.
Bug:
I am unable to destroy the snapshot without rebooting the system.
Status changed to 'Confirmed' because the bug affects multiple users.