You are not logged in.
When the system reaches 'Unmounting network filesystems', it hangs for several minutes, reporting for random shares:
'Could not umount /home/user/smbshare: Device or resource busy'
I looked at what other Linux boxes do in their network filesystem scripts and they run 'umount -l'.
However, when doing that with umount in Archlinux and -t smbfs I get:
usage: smbumount mountpoint
Why does the umount with archlinux call smbumount? And how can I use the lazy flag then to prevent my system from hanging on shutdown?
Offline
You could also try "lsof | grep <busy device>" to see what process is still using your Samba share. After killing the process, the umount command should work fine.
A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
I have pretty much the exact same problem. I can't umount my samba share because it's busy. I can't fuser it, because I get a statting error. And lsof reports that it can't stat the share either, so I don't get information why it's busy. Weee.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline