cryptsetup luksClose cannot close the device despite not being in use
Bug #604909 reported by
Oliver Hookins
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cryptsetup (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: cryptsetup
I have a simple LUKS-encrypted volume, used for taking backups with a simple script:
+ cryptsetup luksOpen /dev/disk/
Key slot 1 unlocked.
+ mount -t ext4 /dev/mapper/
+ /usr/local/
+ umount /media/crypt
+ cryptsetup luksClose iomegacrypt
Device iomegacrypt is busy.
Nothing else uses the device apart from this backup script which is automated and happens shortly after I login. Prior to upgrading to Lucid there was no problem. The output of `lsof` does not show anything using the device.
Revision history for this message
| audience (stefan-sch) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in cryptsetup (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Karl Maier (w-wall2001) wrote | #3 |
To post a comment you must log in.
For me it seems it is not the same bug as #529502 because there is only a bug at the gui and not at the commandline "Manually running cryptsetup luksClose udisks-
But here it is the commandline-tool that is not working.
I got the same problem with the commandline - everything is unmounted but it says device is busy.