Created attachment 573727 [details]
mount.sh (test script)

No, seriously.

After installing cups-1.5.2-6.fc16.x86_64, umounting a loop-device mount will *not* free the loop device, and any attempt to manually delete the loop device returns EBUSY.

I'm attaching the test script that I used while trying to diagnose this problem. In my tests it fails only when cupsd is running. Killing cupsd will allow the test to succeed.

(This actually took me a long time to diagnose because I had so much trouble believing that cupsd was the culprit - I kept starting my tests over because I assumed that I just missed the *real* problem!)