sshfs kernel panic after 10.4.9 update

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Upgrade to 10.4.9 from 10.4.8
2. Use sshfs for your job (ie: constant use all day)

What is the expected output? What do you see instead?
While extensive use of sshfs, with more than 3 files open andbeing actively 
used (.java files in 
TextMate, no file rename, just saves), the kernel panics, and more than once 
per day.  I could use 
sshfs to my heart's content all day on 10.4.8 with no issues.  The kernel panic 
report window 
does not contain anything useful, but for next time I enabled the kernel panic 
output to be 
displayed on screen.

What version of the product are you using? On what operating system?
0.2.2 on 17" PowerBook G4, 1GHz, 1GB RAM
remote system is a linux box (kernel 2.16.16, Fedora Core 4, i686, OpenSSH 
4.2p1, OpenSSL 
0.9.7f)

Please provide any additional information below.
No network issues as mentioned in other Issues(wired and wireless, and I'm the 
sysadmin)

Original issue reported on code.google.com by doktor...@gmail.com on 22 Mar 2007 at 3:08

[GoogleCodeExporter]

I need the kernel panic information for this report to be useful. Isn't your 
/Library/Logs/panic.log capturing the 
panic output?

Original comment by si...@gmail.com on 22 Mar 2007 at 5:57

[GoogleCodeExporter]

Here ya go..

Wed Mar 21 15:12:22 2007
panic(cpu 0 caller 0x000E59C4): vnode_rele_ext: vp 2d1cce4 usecount -ve : -1
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000952D8 0x000957F0 0x00026898 0x000E59C4 0x000F7EB0 0x000F6F80 0x000F62A4 
0x000F2DCC 
         0x002AB7F8 0x000ABB30 0x00000000 
Proceeding back via exception chain:
   Exception state (sv=0x2E7D5000)
      PC=0x90089B0C; MSR=0x0000D030; DAR=0x04EDD000; DSISR=0x42000000; LR=0x00023F24; 
R1=0xBFFFE770; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.9.0: Thu Feb 22 20:54:07 PST 2007; 
root:xnu-792.17.14~1/RELEASE_PPC

Original comment by doktor...@gmail.com on 22 Mar 2007 at 6:00

[GoogleCodeExporter]

This is the same issue as 111.

Original comment by si...@gmail.com on 22 Mar 2007 at 6:24

• Changed state: Duplicate

[GoogleCodeExporter]

Yous ure this is a duplicate?  Issue 111 is with OS 10.4.8 and MacFUSE 0.2.1.  
Maybe it id I don't know.

Original comment by doktor...@gmail.com on 22 Mar 2007 at 7:00

[GoogleCodeExporter]

Yes, it's the same problem. There's a workaround mentioned in the comments for 
111.

Original comment by si...@gmail.com on 22 Mar 2007 at 7:52