chaoyinggg / macfuse

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

-odebug,kill_on_unmount | unmount volume whilst viewing MacFusion Log window | Force Eject dialogue would or could not respond to clicks #191

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Whilst using two options

  -o debug (a FUSE option)
  -o kill_on_unmount (a mount option)

expressed as 

  -odebug,kill_on_unmount 

to troubleshoot a MacFusion issue 
<http://code.google.com/p/macfusion/issues/detail?id=141> 
I seemed to bring upon myself a situation in which I was presented with the 
option to Force Eject, but I could not get the dialogue to respond to clicks. 

<http://code.google.com/p/macfusion/issues/detail?id=141#c3> 
for a _brief_ explanation. 

My concern (I don't know whether it's a valid concern) is that whereas 
on previous occasions the Force Eject option has got me out of sticky 
situations, 
on this occasion I had to remotely ssh in to my unresponsive MacBook 
from a nearby computer on the same LAN to kill -9 the sshfs-static process 
then restart the system, which was acting flaky (for want of a better 
expression). 

Extracts from console.log and system.log are at 
<http://pastie.textmate.org/63158> and 
<http://pastie.textmate.org/private/pxtnzkoe31kw1qev1x> respectively.  

I have more detailed information available, but I shan't append it until I have 
a sense of where we 
might go from here. 

Was 
-odebug,kill_on_unmount 
a reasonable combination of options?

In the help, I note 

> -d   -o debug          enable debug output (implies -f)
 >    -f                     foreground operation

but can't figure whether foreground operation is relevant in this context. 

Was the presence of the MacFusion Log window contributory? 
(I don't expect an answer to the MacFusion question in the 
MacFUSE area. Just wondering.)

Whether or not MacFusion was contributory to the issue in this instance...
might there be ways in which MacFUSE could cope better with 
unexpected or incorrect behaviour of any software that uses MacFUSE as its 
foundation? 
(Easier said than done, I'm sure!)

Regards
Graham

Original issue reported on code.google.com by grahampe...@gmail.com on 20 May 2007 at 10:36

GoogleCodeExporter commented 8 years ago
I've taken care of a few "hang situations" since the last release. Either this 
particular issue shouldn't happen any 
more, or even if it does, it's likely to be because of other reasons since I've 
completely changed some of the code 
that has "hang potential". Please open new issues for new hangs.

Original comment by si...@gmail.com on 20 Sep 2007 at 6:57