cryptsetup luksClose cannot close the device despite not being in use

Bug #604909 reported by Oliver Hookins on 2010-07-13
This bug affects 5 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)

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/by-id/usb-ST925031_5AS_5C75FFFFFFFF-0:0 iomegacrypt -d /root/keyfile
Key slot 1 unlocked.
+ mount -t ext4 /dev/mapper/iomegacrypt /media/crypt
+ /usr/local/sbin/runbackup
+ 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.

audience (stefan-sch) wrote :

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-luks-uuid-[...] afterwards works as expected.".
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.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cryptsetup (Ubuntu):
status: New → Confirmed
Karl Maier (w-wall2001) wrote :

It may be rather be a duplicate of Bug #484429

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers