[Bug 529502] Re: cryptsetup luksClose fails with "busy"

ThorX89 529502 at bugs.launchpad.net
Mon Jan 2 11:14:06 UTC 2012


This bug also affects me. I have an external hardrive with (among other
things) a volume group on it. One of the logical volumes is encrypted
with LUKS and formatted ext4. Whenever I mount it graphically (via
nautilus or the gnome mounting applet), it succeeds (after supplying the
right password), but it behaves kind of oddly. The decrypted volume does
not open "in place" (i.e.: under the icon I clicked on to decrypt it),
but it creates another icon for the decrypted EXT4 drive. The original
icon continues showing the option "Mount volume" (the option "Open
volume" remains grayed out), but I can open the volume via the secondary
icon. I can unmout the volume via the right-click menu of the secondary
icon (causes the secondary icon to disappear) but trying to remount the
the volume via the primary icon fails (even after supplying the right
password) since the cryptsetup partition does not get closed/locked in
/dev/mapper .

As a result
1) the super user (luckily me) can still see my encrypted data. All he has to do is mount the appropriate un(luks)Closed blockdevice in /dev/mapper
2) the owner of the encrypted partition can't reaccess their data without rebooting, unless he's a sudoer who can "cryptsetup luksClose /dev/mapper/uuid* " and do the graphical thing or mount the unlocked cryptsetup partition in /dev/mapper/ .

(P.S. Like khumbartha, I have also encountered the situation several
times where I can't luksClose the the cryptsetup partition, even as the
superuser I don't know how to reproduce it though -- but I think it
happens if the external volume gets unplugged and replugged again an the
logical volumes get reread.)

-- 
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/529502

Title:
  cryptsetup luksClose fails with "busy"

Status in “cryptsetup” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nautilus

  Encrypted LUKS volume lives in /dev/sdb1 (first partition in external
  USB HDD)

  Steps:

  1) Plug USB HDD
  2) Choose Places -> Encrypted volume
  3) Type password in dialog

  Volume is sucesfully mounted and nautilus window is open on mount
  point

  4) Choose File -> Umount

  Expected: partition is unmounted and encryted block device is removed
  from /dev/mapper

  Result: volume is unmouted, cryptsetup fails to remove encrypted block device in /dev/mapper with error:
  Error locking device: cryptsetup exited with exit code 240: Device udisks-luks-uuid-[...] is busy.

  Manually running cryptsetup luksClose udisks-luks-uuid-[...]
  afterwards works as expected.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Feb 28 16:16:53 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100219)
  Package: nautilus 1:2.29.91-0ubuntu1
  ProcEnviron:
   LANGUAGE=es_ES.utf8
   PATH=(custom, user)
   LANG=es_ES.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.32-14-generic x86_64

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




More information about the foundations-bugs mailing list