Open dberzano opened 10 years ago
Similar behaviour here: sshfs on Mavericks works fine with OpenSSH_6.6p1 on Android. The describes problem occurs when the sshd is a Dropbear.
I get exactly the same error with both Dropbear (SSHDroid) and OpenSSH (6.1p1). Both servers work fine and work with ssh, Cyberduck and sshfs on linux (Ubuntu running on VirtualBox).
On OpenSSH I get
$ mkdir -p /Volumes/Phone && sshfs -d root@192.168.1.6:/ /Volumes/Phone/ -osshfs_debug
SSHFS version 2.5
executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-2> <root@192.168.1.6> <-s> <sftp>
Server version: 3
Extension: posix-rename@openssh.com <1>
Extension: statvfs@openssh.com <2>
Extension: fstatvfs@openssh.com <2>
Extension: hardlink@openssh.com <1>
unique: 0, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
remote_uid = 0
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
max_write=0x01000000
unique: 0, error: 0 (Undefined error: 0), outsize: 40
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
[00002] EXTENDED
[00002] STATUS 42bytes (4ms)
unique: 0, error: -102 (Operation not supported on socket), outsize: 16
mount_osxfusefs: failed to mount /Volumes/Phone@/dev/osxfuse1: Operation not supported on socket
sent: 1 messages, 37 bytes
received: 1 messages, 42 bytes
rtt min/max/avg: 4ms/4ms/4ms
num connect: 1
On SSHDroid
$ mkdir -p /Volumes/Phone && sshfs -p 2222 -d root@192.168.1.6:/ /Volumes/Phone/ -osshfs_debug
SSHFS version 2.5
executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-oPort=2222> <-2> <root@192.168.1.6> <-s> <sftp>
SSHDroid
Use 'root' as username
Default password is 'admin'
root@192.168.1.6's password:
Server version: 3
Extension: posix-rename@openssh.com <1>
Extension: statvfs@openssh.com <2>
Extension: fstatvfs@openssh.com <2>
unique: 0, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
remote_uid = 10123
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
max_write=0x01000000
unique: 0, error: 0 (Undefined error: 0), outsize: 40
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
[00002] EXTENDED
[00002] STATUS 42bytes (5ms)
unique: 0, error: -102 (Operation not supported on socket), outsize: 16
mount_osxfusefs: failed to mount /Volumes/Phone@/dev/osxfuse1: Operation not supported on socket
sent: 1 messages, 37 bytes
received: 1 messages, 42 bytes
rtt min/max/avg: 5ms/5ms/5ms
num connect: 1
I get the same issue when trying to mount a phone running OpenSSH from Yosemite.
Same issue here when attempting to connect with sshfs
(recently installed via brew
) to two Android 4.x phones running SSHDroid. ssh
and scp
to the phones work without issues, as does sshfs
to other (non-SSHDroid) hosts. sshfs
to the phones from an Ubuntu client also works without issues. Running OSX Mavericks.
+1, OSX Yositmite 10.10, trying to sshfs into a phone running SSHDroid
sshfs --version
SSHFS version 2.5
OSXFUSE library version: FUSE 2.7.3 / OSXFUSE 2.6.4
no mount point
Please update to the latest version of osxfuse, @dymk. Version 2.6.x has been outdated for a really long time and does not even support Yosemite. Updating osxfuse to the latest version will not fix this issue but it contains a lot of other bugfixes.
+1 OS X 10.11 and latest devel version of spacemacs. Also using OSXFuse 3.7.1
I'm able to browse directories and open files from spacemacs but get the error:
basic-save-buffer-2: Opening output file: Operation not supported on socket, /Users/username/Sites/example.com/mountpoint/testing.txt
I AM able to edit and save this file using vanilla emacs through the command line however. This makes me think the issue is with Spacemacs somehow.
While attempting to mount a certain remote volume:
I am on Mavericks. sshfs version info:
The same volume mounts correctly on Linux:
The remote SSH server runs on an Android device with OpenSSH_6.2p2 and the sftp service works just fine.
I am not sure if this is a sshfs problem or an OSX FUSE problem...
Thanks!