FS#10320 - [truecrypt] "Device busy" when unmounting
Attached to Project:
Arch Linux
Opened by Nicolas Bigaouette (big_gie) - Wednesday, 30 April 2008, 12:43 GMT
Last edited by Allan McRae (Allan) - Monday, 25 January 2010, 07:35 GMT
Opened by Nicolas Bigaouette (big_gie) - Wednesday, 30 April 2008, 12:43 GMT
Last edited by Allan McRae (Allan) - Monday, 25 January 2010, 07:35 GMT
|
Details
Description:
Unable to unmount encrypted files. Truecrypt cries with: umount: /tmp/.truecrypt_aux_mnt1: device is busy umount: /tmp/.truecrypt_aux_mnt1: device is busy See http://bbs.archlinux.org/viewtopic.php?pid=361898#p361898 Additional info: * package version(s) 5.1a-1 * config and/or log files etc. Steps to reproduce: 1) Mount an encrypted file or device to a folder with the GUI. 2) Use any way to unmount it after usage ("Dismount" or "Dismount all" from the GUI, or "Dismount /path/to/encrypted/file" from the tray icon) 3) Truecrypt will seems to freeze, a couple of seconds latter a popup with the error shows up. Note that the encrypted file was created with truecrypt 4.3a. |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 25 January 2010, 07:35 GMT
Reason for closing: No response
Additional comments about closing: No responses in 7 months.
Monday, 25 January 2010, 07:35 GMT
Reason for closing: No response
Additional comments about closing: No responses in 7 months.
==========
I suspect a bug in loop devices on some kernels. I've had similar problems
when mounting and unmounting other sorts of things. The sequence I've
found to "manually" unmount a file mounted via truecrypt is:
sync
umount /secure
losetup -d /dev/loop0
umount /tmp/.truecrypt_aux_mnt1
rmdir /tmp/.truecrypt_aux_mnt1
Sometimes, it seems that the losetup -d won't delete the loop to file
association and fails for no obvious reason. Might want to ask in
some appropriate place for your linux distro and find if there is
a known bug.
==========
I tried and it works.
> sudo umount /tmp/.truecrypt_aux_mnt1
umount: /tmp/.truecrypt_aux_mnt1: device is busy
umount: /tmp/.truecrypt_aux_mnt1: device is busy
Sorry for not having specified this... ;)
Thanx Alessio
Still, looking at the script above, this could probably be fixed(worked around) by passing sync(2) before umount(2) in the truecrypt source, or if that doesn't kill it, in effect recreating that script in the unmount code.
Then frees it up and truecrypt's Dismount button will then work.
http://dpaste.com/hold/75021/
Dunno how relevant it is. Throwing Thomas on here, as I think he knows more about encryption like this than I, and TomK is inactive
At first, I didn't get what bug it refers too, but luckily there's a link to this page in that script.
The following workaround work for me:
sudo umount /dev/loop/0