cryptsetup luksClose foo -> Device foo is busy. (Regression?)

[ewasser]

I'm using FC16 with KDE (Selinux = off) and suddenly (I think after updating via "yum update") the "cryptsetup luksClose foo" returns with the error message

Device foo is busy.

Here are my commands:

% cryptsetup luksOpen /dev/sdg1 foo
% mount /dev/mapper/foo /vols/local/foo
[... COPY FILES...]
% umount /vols/local/foo
% cryptsetup luksClose foo
Device foo is busy.

Why that? How can I release my busy cryptsetup?

I found the following old threads, but nothing helps:

1. Extremely annoying gam_server bug (2005)
2. Help with encrypted stick usage please (2008)
3. Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
4. cryptsetup luksClose cannot close the device despite not being in use

[linceo]

Same problem, F16

[ewasser]

Originally Posted by linceo

Same problem, F16

Bug is gone. After the normal "yum update" routine the bug was fixed(?) and now "cryptsetup luksClose foo" is working like charm.

I'm using now:

cryptsetup-luks-1.3.1-3.fc16.x86_64
cryptsetup-luks-libs-1.3.1-3.fc16.x86_64
kernel-3.3.2-6.fc16.x86_64

I hope that are all releveant patterns.

[ewasser]

The bug is back (with kernel 3.3.6):

cryptsetup-luks-1.3.1-3.fc16.x86_64
cryptsetup-luks-libs-1.3.1-3.fc16.x86_64
kernel-3.3.6-3.fc16.x86_64

Very strange.

[rurikc]

As I posted in another thread:

It may be a kernel bug:

https://bugzilla.redhat.com/show_bug.cgi?id=809188

leading to

https://bugzilla.redhat.com/show_bug.cgi?id=808795

[ewasser]

Thanks for the reply.

It seems that this is the problem: http://www.spinics.net/lists/linux-f.../msg55572.html

[Carrot Cruncher]

i'm running fc17 and had this problem a few months ago. i'm sure it got resolved at some point but i'm now experiencing it again. bug 808795 hasn't been updated for a bit. is anyone else able to confirm ?

cryptsetup-1.4.3-1.fc17.x86_64
cryptsetup-libs-1.4.3-1.fc17.x86_64
kernel-3.4.4-5.fc17.x86_64

[rurikc]

Workaround:

Disable sandbox service.

Sandbox sets up everything as shared:

mount --make-rshared /

A reboot may be necessary.

[Carrot Cruncher]

according to the bug, it's been removed from fc17, i certainly don't have it and can't find anything in the repos.

i'm sure i had this working in fc17 at one point. i only have to do it every so often.

[ewasser]

Originally Posted by rurikc

Workaround:

Disable sandbox service.

I'm sorry, what's the sandbox service?