test forks of MacFUSE for use with sshfs on OS X Lion #1495

Open
opened 2011-08-21 23:15:04 +00:00 by davidsarah · 7 comments
davidsarah commented 2011-08-21 23:15:04 +00:00
Owner

MacFUSE has apparently splintered into three or four forks, none of which work properly with Tahoe on OS X 10.7 (Lion). See wiki/SftpFrontend#sshfsonMacOSX for details.

This ticket can be closed when we are able to access a Tahoe filesystem reliably over sshfs on Lion, and have documented how to do that.

MacFUSE has apparently splintered into three or four forks, none of which work properly with Tahoe on OS X 10.7 (Lion). See [wiki/SftpFrontend#sshfsonMacOSX](wiki/SftpFrontend#sshfsonMacOSX) for details. This ticket can be closed when we are able to access a Tahoe filesystem reliably over sshfs on Lion, and have documented how to do that.
tahoe-lafs added the
code-frontend
major
defect
1.8.2
labels 2011-08-21 23:15:04 +00:00
tahoe-lafs added this to the undecided milestone 2011-08-21 23:15:04 +00:00
davidsarah commented 2011-08-21 23:18:52 +00:00
Author
Owner

Attachment sshfs-debug-output.txt (12407 bytes) added

output of sshfs with -o sshfs_debug, using the Tuxera 2.2.1 fork of MacFUSE. At the end, the sshfs process exits unexpectedly and the filesystem is unmounted.

**Attachment** sshfs-debug-output.txt (12407 bytes) added output of sshfs with -o sshfs_debug, using the Tuxera 2.2.1 fork of MacFUSE. At the end, the sshfs process exits unexpectedly and the filesystem is unmounted.
davidsarah commented 2011-08-21 23:19:55 +00:00
Author
Owner

tarcieri, what was the exact sshfs command line for attachment:sshfs-debug-output.txt?

tarcieri, what was the exact sshfs command line for attachment:sshfs-debug-output.txt?
davidsarah commented 2011-08-22 01:51:55 +00:00
Author
Owner

According to https://trac.macports.org/ticket/29917#comment:48, FUSE4X has already fixed the stability bugs with sshfs and with 64-bit kernels. Also, FUSE4X is forked from a more recent version of Linux FUSE then OSXFUSE, and seems to intend to stay closer to upstream in future (this is supported by the revision histories so far). OSXFUSE seems to have a lone developer (Benjamin Fleischer); although FUSE4X also has one primary developer (Anatol Pomozov), he appears to have more help. OSXFUSE does have the technical advantage of working with existing binaries of filesystems compiled for MacFUSE, but that is liable to cause as many problems as it solves. I'm betting on FUSE4X.

According to <https://trac.macports.org/ticket/29917#comment:48>, FUSE4X has already fixed the stability bugs with sshfs and with 64-bit kernels. Also, FUSE4X is forked from a more recent version of Linux FUSE then OSXFUSE, and seems to intend to stay closer to upstream in future (this is supported by the revision histories so far). OSXFUSE seems to have a lone developer (Benjamin Fleischer); although FUSE4X also has one primary developer (Anatol Pomozov), he appears to have more help. OSXFUSE does have the technical advantage of working with existing binaries of filesystems compiled for MacFUSE, but that is liable to cause as many problems as it solves. I'm betting on FUSE4X.
zooko commented 2011-11-03 04:04:32 +00:00
Author
Owner

Glyph Lefkowitz recommends FUSE4X.

Glyph Lefkowitz recommends FUSE4X.
davidsarah commented 2012-03-27 21:52:40 +00:00
Author
Owner

(wiki/SftpFrontend) was updated to reflect that FUSE4X seems to work: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend?action=diff&version=77&old_version=75

What more, if anything, do we need to close this ticket?

(wiki/SftpFrontend) was updated to reflect that FUSE4X seems to work: <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend?action=diff&version=77&old_version=75> What more, if anything, do we need to close this ticket?
daira commented 2013-05-03 16:57:19 +00:00
Author
Owner

http://fuse4x.github.io/ currently says: "Fuse4X has been merged to OSXFUSE project. Consider switching to OSXFUSE for a new development."

So we need to test OSXFUSE (a.k.a. FUSE for OS X), and then update wiki/SftpFrontend to recommend that if it works.

<http://fuse4x.github.io/> currently says: "Fuse4X has been merged to [OSXFUSE](http://osxfuse.github.io/) project. Consider switching to OSXFUSE for a new development." So we need to test [OSXFUSE](http://osxfuse.github.io/) (a.k.a. FUSE for OS X), and then update [wiki/SftpFrontend](wiki/SftpFrontend) to recommend that if it works.
tahoe-lafs added
task
and removed
defect
labels 2013-05-03 16:57:19 +00:00
daira commented 2013-05-03 17:02:49 +00:00
Author
Owner
See also <https://groups.google.com/forum/#!topic/fuse4x/Pi55U_K4HgU>.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1495
No description provided.