Comment 8 for bug 917339

Revision history for this message
Carlos Garza (carlos-garza) wrote :

I'm on 12.04

in my case I'm seeing libvirtd continuesly respawning and mounting the device some how.
umount /var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev
root@bork:~# lsof | grep /var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev
dbus-daem 19780 messagebus 0u CHR 1,3 0t0 5826 /var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev/nul
tgtd 19794 root 0u CHR 1,3 0t0 5826 /var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev/null
libvirtd 19913 root 0r CHR 1,3 0t0 5826 /var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev/null

usually attempting to kill the processes just ends up in them respawning and magically remounting the directories. I can tell this by
I see message in dmesg to the effect of libvirt-bin terminated. Then right below it I see another message saying libvirtd-bin process e ended respawning.

The main culprits is usually udev though.

rebooting is problematic too if the schroot daemon picks up old sessions in the /var/lib/schroot/sessions directory and mounts those directories. :|

Seems the only sure fire way I've found is to delete the sessions directory and reboot. then I can umount them. And yes they misteresly are mounted some how.

I can't ease the schroots root directory unless I do this process and I was useing schroot so I could quickly ease a linux environment and start from scratch. Whats the status on this bug. It seems like the inability to forcefully umount the directories is the main cause of head ache.