I'll improve it, with a umount hook that tries regular umount before lazy umount. If regular umount fails we know it is busy somehow, so that's something to fall back to even if my other checks can not find all reasons as to why it is busy.
Unfortunately the kernel does not make it easy to track filesystems that it is still using in read-write mode but not bound to any real VFS path. lazy umount is really really bad idea
|