Ok, I don't know how I ended up in this situation
exactly. It involved lufsd debugging, some mounted
filesystems, a crash in lufsd
Anyway, I end up with a directory that can not be
umount: blah: device is busy
I carefully checked that all processes which may have
been locking stuff in there are dead (including the
Module Size Used by Not tainted
lufs 13152 3
I can't rmmod lufs, I can umount that dir either .. I
feel kinda stuck into rebooting now :-)
what kind of solution could we have to prevent stalls
like that, or diagnose the kernel module, etc.? maybe
we could have something in /proc ?
Log in to post a comment.