Long delay unmounting remote filesystems on shutdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysvinit (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi all.
I have two machines with Dapper Drake (one dist-upgraded from breezy when dapper was beta and another installed from scratch from the final 6.06 LTS CD). Both machines are up-to-date.
The problem occours when I leave samba shares mounted and I shut down Ubuntu. "Unmounting remote filesystems..." takes a lot . It switches to text mode and shows:
[4294848.96900] CIFS VFS: No response for cmd 50 mid 46
[4294908.96900] CIFS VFS: No response for cmd 50 mid 223
'mid' number is different each time. The delay may be of 2 minutes on a Celeron M370.
I use mount.cifs (suid root) in order to mount five W2K3 shares, over a wireless connection using wifi-radar for roaming.
If I call the umountnfs.sh script from console as root:
# /etc/init.
it does nothing.
Note that the same scripts we user for mounting that shares works perfectly on a Fedora Core 5 machine, and it shuts down fast and cleanly. The only difference is that wifi-radar is not used on that laptop.
I hope this is a duplicate of a solved bug, but I haven't found it!
Cheers.
I have this happening too, when connecting to a share using cifs over a wireless connection (WPA with Network Manager)
I'm running Dapper Drake 6.06LTS with the latest updates.
I don't know exactly how long the umounting takes, since I assumed it had hung and so I shut it off manually (power button held down).
Maybe the solution is to either disconnect all mounted network shares before turning off the network connection (either wired or wireless) or have the cifs umount program not wait for a response (since there is no route to host anyway!).
Cheers,
Vipul