Opened 13 years ago

Closed 13 years ago

#31768 closed defect (invalid)

kernel panic when touch file in filesystem mounted with sshfs

Reported by: gallafent Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: lion Cc: anatol (Anatol Pomozov)
Port: sshfs

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Hi All,

When I try to touch a file in a filesystem mounted using sshfs, the machine crashes hard, requiring four-second-button-press.

I cleaned and reinstalled sshfs and its dependencies. The install process went like this: 

MyMac:~ williamg $ sudo port install sshfs
--->  Computing dependencies for sshfs
--->  Dependencies to be installed: fuse4x fuse4x-kext
--->  Fetching archive for fuse4x-kext
--->  Attempting to fetch fuse4x-kext-0.8.12_0+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/fuse4x-kext
--->  Fetching fuse4x-kext
--->  Attempting to fetch fuse4x-kext-0.8.12.tar.gz from http://lil.fr.distfiles.macports.org/fuse4x-kext
--->  Verifying checksum(s) for fuse4x-kext
--->  Extracting fuse4x-kext
--->  Applying patches to fuse4x-kext
--->  Configuring fuse4x-kext
--->  Building fuse4x-kext
--->  Staging fuse4x-kext into destroot
--->  Installing fuse4x-kext @0.8.12_0+universal
--->  Activating fuse4x-kext @0.8.12_0+universal
--->  Cleaning fuse4x-kext
--->  Fetching archive for fuse4x
--->  Attempting to fetch fuse4x-0.8.12_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/fuse4x
--->  Fetching fuse4x
--->  Attempting to fetch fuse4x-0.8.12.tar.gz from http://lil.fr.distfiles.macports.org/fuse4x
--->  Verifying checksum(s) for fuse4x
--->  Extracting fuse4x
--->  Applying patches to fuse4x
--->  Configuring fuse4x
--->  Building fuse4x
--->  Staging fuse4x into destroot
--->  Installing fuse4x @0.8.12_0
--->  Activating fuse4x @0.8.12_0
--->  Cleaning fuse4x
--->  Fetching archive for sshfs
--->  Attempting to fetch sshfs-2.3_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/sshfs
--->  Fetching sshfs
--->  Verifying checksum(s) for sshfs
--->  Extracting sshfs
--->  Applying patches to sshfs
--->  Configuring sshfs
--->  Building sshfs
--->  Staging sshfs into destroot
--->  Installing sshfs @2.3_0
--->  Activating sshfs @2.3_0
--->  Cleaning sshfs

As you can see, all the dependencies were installed fresh.

However, the hard crash results. I will attach a sample session (in which I simply mount the remote fs with -d in case that's of any use), and the kernel crash log which is presented to me after the reboot! If instead of attempting to use it, I unmount the filesystem using umount, the sshfs process terminates and all is well!

Attachments (2)

session​ (4.6 KB) - added by gallafent 13 years ago.
console output during mount process with -d debug flag
crashlog​ (7.4 KB) - added by gallafent 13 years ago.
Fresh crash log after update to fuse4x 0.8.13

Download all attachments as: .zip

Change History (8)

Changed 13 years ago by gallafent

Attachment: session​ added

console output during mount process with -d debug flag

comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: dports@… openmaintainer@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to dports@…

Sounds like a bug that should be reported to the developers of sshfs.

comment:3 Changed 13 years ago by gallafent

… and further upstream: ​https://github.com/fuse4x/fuse4x/issues/16

Changed 13 years ago by gallafent

Attachment: crashlog​ added

Fresh crash log after update to fuse4x 0.8.13

comment:4 Changed 13 years ago by gallafent

(Installation log, for completeness): 

--->  Fetching archive for fuse4x-kext
--->  Attempting to fetch fuse4x-kext-0.8.13_0+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/fuse4x-kext
--->  Fetching fuse4x-kext
--->  Attempting to fetch fuse4x-kext-0.8.13.tar.gz from http://lil.fr.distfiles.macports.org/fuse4x-kext
--->  Verifying checksum(s) for fuse4x-kext
--->  Extracting fuse4x-kext
--->  Applying patches to fuse4x-kext
--->  Configuring fuse4x-kext
--->  Building fuse4x-kext
--->  Staging fuse4x-kext into destroot
--->  Installing fuse4x-kext @0.8.13_0+universal
--->  Cleaning fuse4x-kext
--->  Deactivating fuse4x-kext @0.8.12_0+universal
--->  Cleaning fuse4x-kext
--->  Activating fuse4x-kext @0.8.13_0+universal
The Fuse4X kernel extension is already loaded. Attempting to unload it.
Successfully unloaded the previous installation of Fuse4X
--->  Cleaning fuse4x-kext
--->  Computing dependencies for fuse4x
--->  Fetching archive for fuse4x
--->  Attempting to fetch fuse4x-0.8.13_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/fuse4x
--->  Fetching fuse4x
--->  Attempting to fetch fuse4x-0.8.13.tar.gz from http://lil.fr.distfiles.macports.org/fuse4x
--->  Verifying checksum(s) for fuse4x
--->  Extracting fuse4x
--->  Applying patches to fuse4x
--->  Configuring fuse4x
--->  Building fuse4x
--->  Staging fuse4x into destroot
--->  Installing fuse4x @0.8.13_0
--->  Cleaning fuse4x
--->  Computing dependencies for fuse4x
--->  Deactivating fuse4x @0.8.12_0
--->  Cleaning fuse4x
--->  Activating fuse4x @0.8.13_0
--->  Cleaning fuse4x

comment:5 Changed 13 years ago by anatol (Anatol Pomozov)

Cc: anatol.pomozov@… added

Cc Me!

comment:6 Changed 13 years ago by drkp (Dan Ports)

Resolution: → invalid
Status: new → closed

Since this is reported upstream, that's probably a better place to track the issue than here.

Note: See TracTickets for help on using tickets.