lifearttw / macfuse

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

SSHFS cause system to freeze if network config changes #127

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Mount a remote volume in SSHFS
2. Change Location or change network config before unmount SSHFS volumes

What is the expected output? What do you see instead?
The Finder and the System freeze, after that, methods including
umount/Ejecting/Relaunch Finder/Restart will still fail. Need to press the
power button to shut it down.

What version of the product are you using? On what operating system?
MacFuse Core 0.2.2 SSHFS 0.1.0 Mac OSX 10.4.9

I'm using a Macbook and have to change locations often. It happens sometime
I forget to umount the SSHFS Volumes before I close the lid and go, but I
will pay something terrible for the carelessness.

Original issue reported on code.google.com by chumsd...@gmail.com on 16 Mar 2007 at 7:13

GoogleCodeExporter commented 8 years ago
Did the Finder "freeze" or the entire user interface (or operating system) 
hung? If you are able to try to run 
umount from the command line, then the operating system isn't hung, I presume.

Anyway, please search in the past issues list and on the macfuse-devel mailing 
list. This topic (network 
disruption causing the Finder to hang, etc.) has come up many, many times. 
There are possible workarounds, 
including a timeout you can set after which a "frozen" volume will 
automatically eject.

Original comment by si...@gmail.com on 16 Mar 2007 at 11:59

GoogleCodeExporter commented 8 years ago
I've experienced the same thing multiple times... if I forget to unmount my 
work volumes before I go home for 
the day (macbook) I run into the same thing once starting up again at home. 
However I've never had to reboot... 
fire up a terminal and kill the sshfs processes and problems gone.

Original comment by joachim....@gmail.com on 24 Mar 2007 at 10:36

GoogleCodeExporter commented 8 years ago
This happens to me all the time, i often have to switch between different 
wireless
connections at work and every time i do it w/o unmounting my sshfs volumes first
finder and everything that uses finder freezes.

if you try to do something related to finder, like send a file with gmail in 
firefox,
firefox freezes when trying to open the "open file" dialog, etc..

however, after a while a dialog asking for my sshfs password pops up and after 
i type
in my password and press enter everything starts working again.

i used to do hard resets in the beginning but now i just wait for the dialog to 
pop up.

Original comment by carl.jo...@gmail.com on 28 Mar 2007 at 6:05

GoogleCodeExporter commented 8 years ago
I have also experienced this, indeed it is the main thing that discourages me 
from
using sshfs, which is otherwise something I have long hoped for.

If I connect to a remote server, then go to sleep, wake up somewhere else and 
connect
to a different wireless network, finder freezes, Quicksilver crashes (may or 
may not
be related), and even doing a forced restart on finder doesn't fix the problem. 
 The
only way I have found to restore my system to normal operation is a reboot.

Original comment by ian.clarke on 14 Apr 2007 at 10:59

GoogleCodeExporter commented 8 years ago
Have you looked at the MacFUSE FAQ?

====
Q: When I have an SSHFS volume mounted and something happens to the connection 
(or my computer wakes 
up from sleep), the Finder beachballs. Can I do something about this?

A: 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.
====

Original comment by si...@gmail.com on 18 Apr 2007 at 7:57

GoogleCodeExporter commented 8 years ago
The just released update to SSHFS might be helpful to you.

Original comment by si...@gmail.com on 19 Apr 2007 at 9:43

GoogleCodeExporter commented 8 years ago
For now, the best MacFUSE can do is to let you specify a timeout (10 seconds by 
default) within which the user 
space file system daemon must respond. If it doesn't, the Finder will start 
beachballing, but you'll be able to eject 
the volume if you so wish (and the Finder will stop beachballing). An alert 
panel for this purpose was added in 
MacFUSE 0.2.5. Rather than "fixed", I'm marking this as duplicate because there 
are multiple instances of this 
"issue" (or variant) present in the system.

Original comment by si...@gmail.com on 2 May 2007 at 5:33

GoogleCodeExporter commented 8 years ago

Original comment by si...@gmail.com on 2 May 2007 at 5:33