mukulyadav49 / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

SSHFS: Connection drop with active mount causes finder and associated applications to freeze #134

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
1. Mount drive with SSHFS
2. Open subfolder on drive, open file for editing
3. Disable connection

I would expect the mounted drive to disappear.  Instead Finder, my editor,
and interestingly Quicksilver, all freeze.  Relaunching/Force quitting is
not successful, as they seem to hang again on restart.  Shutdown/restart
all hang requiring a hard restart.

MacFUSE-Core-0.2.2.dmg
sshfs-0.1.0.dmg
OS X 10.4.6

If I have Activity Monitor open, I can force quit the sshfs-static process
which does not exit.  This can prevent the ned for a hard restart as it
frees many of the applications, but I have noticed significant system
instability.  This issue is likely related to #113 and #114.

Original issue reported on code.google.com by tfwri...@gmail.com on 28 Mar 2007 at 5:51

GoogleCodeExporter commented 9 years ago
If you know it's a network connection drop, then it's not related to #113.

sshfs behavior on network connection disruption has been discussed many, many 
times. Search in the mailing 
list and in the past issues. In a pinch, here's the FAQ entry on this:

==
Try using the -o reconnect option to sshfs. MacFUSE Core 0.1.9 introduced 
better Finder interaction, along 
with the -o daemon_timeout option that lets you specify a hard upper limit 
after which a "hung" volume will 
be automatically ejected. You can also try to kill the file system process 
(sshfs, in this case) -- you might have 
to kill -9.
==

Don't force quit--try going to the Terminal and "kill -9" the sshfs process.

What you expect ("the mounted drive to disappear") is not reasonable from a 
file system standpoint, even 
though the resultant behavior (things apparently freezing) is hardly desirable. 
If you do want the volume to 
auto-eject, just use the daemon_timeout option.

Original comment by si...@gmail.com on 28 Mar 2007 at 10:50