SSHFS stalls Finder indefinitely after network connection reset

[GoogleCodeExporter]

I realize this is likely a Finder and Disk Arbitration issue, and that MacFUSE 
might not be able to 
work around this, but if there is a way…

What steps will reproduce the problem?
1. Use SSHFS to connect to a remote server. Make sure it has mounted correctly 
in Finder.
2. Disconnect (for example, turn off AirPort / unplug your Ethernet cable / 
etc.).
3. After a while, reconnect.

What is the expected output? What do you see instead?
Either, once the connection has "recovered", it should be possible again to 
browse the file 
system, or the Finder should unmount it automatically once the connection is 
gone. In either 
case, the Finder should never stall.

Instead, the Finder stalls, and continues to do so for minutes. Only killing 
and relaunching fixes 
this, after which the file system can be ejected and re-mounted.

What version of the product are you using? On what operating system?
fuse-binaries-0.1.0b006.tar.bz2 binary tarball, Mac OS X 10.4.8 (8L2127), 
MacBookPro1,1.

Original issue reported on code.google.com by chucker...@gmail.com on 12 Jan 2007 at 10:05

[GoogleCodeExporter]

Unfortunately, the Finder is very sensitive to filesystems being unavailable. 
There
is little we can do about it in fuse.

I'm sorry, but you'd have to take it up with Apple.

Original comment by motown...@gmail.com on 12 Jan 2007 at 10:27

• Changed state: Invalid

[GoogleCodeExporter]

motownavi, in my experience sensitivity to unavailable filesystems doesn't end 
at
Finder: my terminal session also hangs when trying to browse an unavailable FS. 
In
most cases, Ctrl-C cancels the offending operation, but I'm unable to "umount"
network filesystems until session connectivity has been restored. This is a big
problem for me as one of the servers I've mounted drops idle SSH sessions! Would
'keep alive' functionality to SSHFS be outside the scope of MacFUSE?

Original comment by contact%...@gtempaccount.com on 24 Jan 2007 at 5:45