Kernel crash using sshfs over fuse4x when attempting to touch a file

[gallafent]

Full details here:
https://trac.macports.org/ticket/31768

Let me know if any other details are required!

[gallafent]

Updated to fuse4x 0.8.13 today via MacPorts. Same problem persists. I will attach the kernel crash report to the macports ticket (since I don't see a way to attach a file here!).

[anatol]

Hi,

Thanks for reporting. I do not see what kext failed but if it is fuse4x then it is definitively bug that should be fixed.

First of all https://trac.macports.org/attachment/ticket/31768/session shows that you use libfuse from fuse4x-0.8.12. I suggest to restart computer to make sure that all previous usages of fuse4x unloaded and the new version of fuse4x is in use (you should see "FUSE library version: 2.8.6" on the top of https://trac.macports.org/attachment/ticket/31768/session).

I just checked "touch ..." and works fine for me on 10.6.8. I see that you use 10.7.2 - I'll test it later.

[anatol]

If you still see the issue after restart could you please uninstall sshfs, fuse4x, fuse4x-kext ports and install fuse4x from *.dmg file to see if the issue still exist:

cd ~/Downloads
wget https://github.com/downloads/fuse4x/fuse4x/Fuse4X-0.8.13.dmg
open Fuse4X-0.8.7.dmg
wget https://github.com/downloads/fuse4x/fuse4x/sshfs-2.3.0.zip
unzip sshfs-2.3.0.zip -d /

[anatol]

And one more question if you don't mind - do you see that kernel panic if you load with 64bit kernel? (32 and 64 bit kernel extensions are bit different.)

[anatol]

I just built sshfs from macports on my macosx 10.7.2 32bit and sshfs works fine. I run

sshfs -d locahost: tmpdir

When I stop sshfs process by Ctrl+Z then the system hangs, but it is expected as some internal filesystem requests (e.g. by Finder) cannot be processed by fuse. But I do not see any kernel panics.

Do you see the same issue on other computers? Does anybody else sees it? Any more detailed steps to reproduce it? Could you try to mount sshfs to localhost?

BTW show me your ssh version "ssh -v".

[gallafent]

Hi, I will try to reply to your posts in order, and in full, so I don't miss anything!

So, the first one, @“Thanks for reporting”: I have tried again with 0.8.13 (without a restart), and the crash log is now attached to the macports ticket: https://trac.macports.org/attachment/ticket/31768/crashlog … I didn't update the session file though. I will update the session log later today.

Note that according to the crash log, the recent kext activity was that fuse4x 0.8.12 was unloaded, and fuse4x 0.8.13 was loaded, so I'm pretty sure that the right version was there. I'll try again later today including a restart, though!

Regarding 64-bit kernel, I can't do that on this machine since it's a Mac Pro 1.1, which has only 32-bit EFI, and thus can't launch the 64-bit kernel! Not sure whether I can on the MacBook, but I'll take a look (but does 10.6 have a 64-bit kernel available?)

So, my actions:
• Try out again after restarting the computer, confirming I am really using fuse4x 0.8.13
• Try removing the tools from macports and using those from the dmg/zip distributions

• Try on another computer (I have a MacBook running 10.6.latest, I can try there)
  • Try mounting a filesystem on the local machine rather than remote

Anything else? I'll post results later.

[gallafent]

Oh yes, ssh version:

Humber:~ williamg$ which ssh
/opt/local/bin/ssh
Humber:~ williamg$ ssh -v
OpenSSH_5.9p1, OpenSSL 1.0.0e 6 Sep 2011

[gallafent]

Final thought for now: Could there be a problem when e.g. my kernel is 32-bit, but I'm running 64-bit userspace, as is the norm on a computer like mine?

/opt/local/bin/sshfs: Mach-O 64-bit executable x86_64
Humber:~ williamg$ file /opt/local/bin/ssh
/opt/local/bin/ssh: Mach-O 64-bit executable x86_64

[anatol]

Yes it is normal. Many people (including me) run 64 userspace with 32bit
kernel.
On Oct 27, 2011 2:25 AM, "gallafent" <
reply@reply.github.com>
wrote:

Final thought for now: Could there be a problem when e.g. my kernel is
32-bit, but I'm running 64-bit userspace, as is the norm on a computer
like mine?

/opt/local/bin/sshfs: Mach-O 64-bit executable x86_64
Humber:~ williamg$ file /opt/local/bin/ssh
/opt/local/bin/ssh: Mach-O 64-bit executable x86_64

--
Reply to this email directly or view it on GitHub:
#16 (comment)

[anatol]

Hi, any news?

[gallafent]

On 4 November 2011 03:42, Anatol
reply@reply.github.com
wrote:

Hi, any news?

Haven't got to it yet, sorry! Will try to investigate this weekend.
Thanks for your patience :)

Bill Gallafent.

[anatol]

Cannot reproduce it. Please test the latest release (0.9.1) and reopen the ticket if the issue still exists.