[Bug 604909] Re: cryptsetup luksClose cannot close the device despite not being in use

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 529502 ***
    https://bugs.launchpad.net/bugs/529502

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

** Changed in: cryptsetup (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/604909

Title:
  cryptsetup luksClose cannot close the device despite not being in use

Status in “cryptsetup” package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/604909/+subscriptions