cryptsetup luksClose fails with "busy"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
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-
Manually running cryptsetup luksClose udisks-
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=
PATH=(custom, user)
LANG=es_ES.utf8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: nautilus
Uname: Linux 2.6.32-14-generic x86_64
Changed in nautilus (Ubuntu): | |
importance: | Undecided → Low |
assignee: | nobody → Ubuntu Desktop Bugs (desktop-bugs) |
summary: |
- Cannot umount LUKS volume from USB HDD + cryptsetup luksClose fails with "busy" |
I tried this on current lucid with an USB stick (single partition, encrypted LUKS VFAT), and it works fine for me. Both with right click -> unmount and with the eject symbol in nautilus' bookmarks. Thus I need some further debug information from you, I'm afraid.
Please start with a clean slate, i. e. reboot or cryptsetup luksClose, so that /dev/mapper/ only has control. Now open a terminal and do
udevadm monitor -e --udev >/tmp/udev.log 2>&1 & udisks/ udisks- daemon --replace 2>&1 | tee /tmp/udisks.log
sudo /usr/lib/
Now reproduce the situation, i. e. mount and unmount the partition, and verify that you get the cryptsetup failure.
Please press Control-C, do "fg", Control-C again, and attach /tmp/udisks.log and /tmp/udev.log here. Thanks!