Comment 21 for bug 579858

I did a couple of tests yesterday on my automounted nfs share, and it appeared to have fixed the segfault there.
However, today when I shut down I pressed 'Esc' to see the messages and I got a very brief glimpse of a message about the / mount being busy, maybe something else (can't say if it was a segfault message) and then the machine powered off immediately. On restarting, I found messages in syslog about orphaned inodes in the root file system, THAT IS BAD!
My own system is running 32-bit 10.04 and I have separate partitions for /, /tmp, and /home, so most likely the file(s) in use for / were log messages (pulseaudio is particularly bad at loads of pointless rate limiting messages, etc, and I had been doing stuff with sound). But there is no excuse for not unmounting properly!
Given the report of Etienne Goyer, and my experience today, there is clearly something still not correct about umount.