Mustafa COMOGLU | 30 Apr 17:10 2015

share with symbolic links

I used this command to share my storage to another machine but it does not
allow me to share the storage with symbolic links? How can I allow to share
the symbolic links as well like the other folders?

sshfs -o allow_other -o ro sysop <at> koeri-arch:/mnt/mSEED_data/archive

​thanks in advance​



Mustafa ÇOMOĞLU / Geophysicist/Jeofizik Mühendisi

BOUN KOERI/ B.Ü. KRDAE Ulusal Deprem Izleme Merkezi

T: comoglu <at>  e: +90216 5163269
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.;117567292;y
Fuse-sshfs mailing list
Fuse-sshfs <at>
(Continue reading)

Peter Möller | 27 Mar 14:46 2015

sshfs-*server* on OS X?


This is not a bug, so I might be in the wrong place.
I would like to get a sshfs-*server* running on an OS X machine (a server, in fact) but I cannot find any
information on that. Finding the sshfs-*client* for OS X is easy enough, but the server is highly elusive. 

I do not understand what is required, nor can I find any source for it. It is based on scp/ssh, right? OS X uses
OpenSSH, so that should be covered. What else is required?

With kind regards,
/Peter Möller
Peter.Moller <at>, Computer Systems Manager
Department of Computer Science, Lund University
Box 118, S-221 00 LUND, Sweden, tfn +46 46 222 41 56

Attachment (smime.p7s): application/pkcs7-signature, 5811 bytes
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now.
Fuse-sshfs mailing list
Fuse-sshfs <at>
(Continue reading)

Sverd Johnsen | 26 Mar 15:52 2015

O_TMPFILE on sshfs?

A program I use tries this on sshfs and fails:

not supported)

On non-sshfs it does this:

open("/tmp/2001/test/incoming", O_WRONLY|O_DIRECTORY|O_CLOEXEC|O_TMPFILE) = 4
sendfile(4, 3, [0], 95476)              = 95476
linkat(AT_FDCWD, "/proc/self/fd/4", AT_FDCWD,
"/tmp/2001/test/incoming/foobar", AT_SYMLINK_FOLLOW) = 0

So I guess O_TMPFILE is not supported at this point?

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now.
"Mario A. Valdez-Ramírez" | 19 Mar 13:42 2015

Bug report: passwords longer than 64 characters from stdin

Fuse SSHFS maintainers:

   Hi. This is a bug report for handling passwords longer than 64
characters from stdin.

If sshfs is called with the "password_stdin" option (for example, when
invoked with pam_mount) it will refuse to accept a password longer
than 64 characters.

The limit is hardcoded in the sshfs.c file (line 3069 in version 2.3,
line 3466 in version 2.5) with the variable named "max_password".

To reproduce, from the command-line you can use for example:

sshfs mvaldez <at> servername:/home/mvaldez/SHARE ./myfiles -o

then type the password (sshfs will wait for the password from stdin
without prompt) and press Enter. If the password is longer than 64
characters it will fail with the message: "Password too long".

When used with pam_mount, the logs in /var/log/auth.log show the
following messages:
pam_mount(mount.c:69): Messages from underlying mount program:
pam_mount(mount.c:73): Password too long
pam_mount(pam_mount.c:521): mount of
sshfs#mvaldez <at> servername:/home/mvaldez/SHARE failed

This limit seems to be inherited from the first patches sent to the
(Continue reading)

Josh Lovins | 10 Mar 18:51 2015

Getting slow speeds in sshfs

When copying files from a sshfs mount to the local drive, my speeds are way
slower than if i were to use scp or sftp.

The versions I'm using of sshfs and fuse is

SSHFS version 2.5

FUSE library version: 2.9.2

fusermount version: 2.9.2

using FUSE kernel interface version 7.19

I'm also using the hpn patched ssh with version

OpenSSH_6.6.1p1-hpn14v5 Ubuntu-5hpn14v5~wrouesnel~trusty2, OpenSSL 1.0.1f 6
Jan 2014

located from

I've tweaked my TCP window sizes and options with these below in



net.ipv4.tcp_rmem= 20480 174760 25165824
(Continue reading)

Linda Burchi | 4 Mar 17:14 2015

issue connecting remote disks - help on bug - NoMachine

my name is Linda Burchi, I am a project manager in
We currently have one trouble report which could be related to a bug in 
your code.
We are using sshfs (2.4 version) with fuse (2.9.0 version) to connect 
remote disks. We noticed some problems while refreshing content of 
connected disks. When we connect a disk from a computer A (linux 64bit) 
to a computer B (linux 64bit) and  we add some files to the remotely 
connected disk on computer A, this files are not visible in 
terminal/file managers on computer B. Refreshing content in file manager 
doesn't solve this problem. We tried different sshfs options when 
connecting disks and none of them solves our problem.
I put in copy Michal Czyrski, a developer who is working on this TR, 
feel free to contact him if you need further information and details.
Please take into account that we have a testing team and it is not a 
problem for us to test a patch and check if it fixes the bug.
Any feedback and comments would be highly appreciated.
Best regards,
Linda Burchi

This email is free from viruses and malware because avast! Antivirus protection is active.

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
(Continue reading)

dbacc | 20 Feb 17:02 2015

Problems establishing connection after password prompt


I'm trying to mount a remote folder via sshfs on arch with current software.

User on the server side is different from local user.

After entering sshfs -C userserver <at> server:serverfolder clientfolder I
get the password promptfor userserver. Then nothing more happens, i.e.
the shell does not return. So after help from the arch forums I tried
again with debug informations (-d and -o LOGLEVEL=DEBUG3) turned on .
Unfortunately this does not solve my problem, since for me there is no
useful information. Apparently at some stage after login prompt it gets

debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 0
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to client.
debug2: fd 4 setting O_NONBLOCK
debug3: fd 5 is O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Requesting no-more-sessions <at>
debug1: Entering interactive session.
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: packet_set_tos: set IP_TOS 0x08
debug2: client_session2_setup: id 0
(Continue reading)

Roland Koebler | 20 Feb 13:34 2015

sshfs, hardlinks and use_ino


I think I've found a bug in SSHFS:

- I can create hardlinks over SSHFS, but by default, stat then reports
  different inodes for the original file and the hardlink!
  (This behavior is very strange by itself, and I would consider it a
  bug by itself, since it breaks the definition of a hardlink.)

- "-o use_ino" should fix this, but when I try to mount with this
  option, the mount seems to fail silently (no error-message, mounted
  according to "mount", but there are no files).

This should be fixed, so that either hardlinks work correctly (and stat
reports the same inode-numbers for hardlinks), or that sshfs fails when
trying to create a hardlink.

Note: This e.g. means that you cannot use mutt with maildirs over sshfs
      anymore, since mutt tries to hardlink a file and then compares the
      inodes; and if they don't match, mutt will hang/loop and create
      thousands (or more) of hardlinks until mutt is killed.
      (Related Debian-bug-number: #778801)

Tested with SSHFS on Debian (both Wheezy/stable and testing):
- SSHFS version 2.4
  FUSE library version: 2.9.0
  fusermount version: 2.9.0
  using FUSE kernel interface version 7.18
- SSHFS version 2.5
  FUSE library version: 2.9.3
(Continue reading)


gnome-keyring daemon fails on SSHFS

Hi, is it possible for this bug to get solved from the SSHFS side instead
of the gnome-keyring side?

I don't know if the GNOME developers are willing to fix it in gnome-keyring
if they consider it a bug in SSHFS, but if it is a limitation in SFTP and
can't be fixed in SSHFS, we'll have a better chance of convincing them...

Thank you!
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
leecholho | 26 Nov 01:53 2014

help: sshfs error

i use sshfs and i get error message . this is bug?
And this is connection command.sshfs  root <at> staging:/opt/XXXX/current/app/webroot
/opt/XXXX/current/app/webroot -o IdentityFile=/root/.ssh/sshfs,allow_other,uid=48,gid=48
-odebug,sshfs_debug,loglevel=debug -f
this is error logLOOKUP /img/city/T00018/T00018_xl.jpggetattr /img/city/T00018/T00018_xl.jpg  
NODEID: 18914   unique: 49919025, success, outsize: 144unique: 49919026, opcode: READDIR (28), nodeid:
18900, insize: 80, pid: 18043   unique: 49919026, success, outsize: 16unique: 49919027, opcode:
RELEASEDIR (29), nodeid: 18900, insize: 64, pid: 0   unique: 49919027, success, outsize: 16unique:
49919028, opcode: GETATTR (3), nodeid: 18904, insize: 56, pid: 18043getattr /img/city/T00010   unique:
49919028, success, outsize: 120unique: 49919029, opcode: OPENDIR (27), nodeid: 18903, insize: 48,
pid: 18043   unique: 49919029, success, outsize: 32unique: 49919030, opcode: READDIR (28), nodeid:
18903, insize: 80, pid: 18043getdir[0][12799440] OPENDIR  [12799437]         STATUS       32bytes (0ms)  [1
 2799438]         STATUS       32bytes (0ms)  [12799439]         STATUS       28bytes (0ms)  [12799440]         HANDLE       17bytes
(0ms)[12799441] READDIR[12799442] READDIR  [12799441]           NAME      815bytes (0ms)  [12799442]         STATUS       32bytes
(0ms)[12799443] READDIR[12799444] READDIR  [12799443]         STATUS       32bytes (0ms)  [12799444]         STATUS      
32bytes (0ms)*** glibc detected *** sshfs: double free or corruption (out): 0x00007f34440be390
***======= Backtrace: =========/lib64/[0x7f344c37f166]/lib64/[0x7f344c381c93]sshfs[0x4046a4]sshfs[0x406872]sshfs[0x40b384]/usr/lib/[0x7f344cfd5065]/usr/lib/[0x7f344cfdc009]/usr/lib/[0x7f344cfe0e16]/usr/l

Memory map: ========00400000-00410000 r-xp 00000000 08:01 340943                            
/usr/local/bin/sshfs0060f000-00610000 rw-p 0000f000 08:01 340943                            
/usr/local/bin/sshfs00610000-00611000 rw-p 00000000 00:00 001765000-0180a000 rw-p 00000000 00:00
0                                  [heap]7f3428000000-7f3428105000 rw-p 00000000 00:00 07f3428105000-7f342c000000 ---p 00000000
00:00 07f342c000000-7f342c1bd000 rw-p 00000000 00:00 07f342c1bd000-7f3430000000 ---p 00000000
00:00 07f34335ff000-7f3433600000 ---p 00000000 00:00 07f3433600000-7f3434000000 rw-p 00000000
00:00 07f343
 4000000-7f34341f0000 rw-p 00000000 00:00 07f34341f0000-7f3438000000 ---p 00000000 00:00
07f3438000000-7f3438190000 rw-p 00000000 00:00 07f3438190000-7f343c000000 ---p 00000000 00:00
07f343c000000-7f343c021000 rw-p 00000000 00:00 07f343c021000-7f3440000000 ---p 00000000 00:00
(Continue reading)

Transport endpoint is not connected

i use sshfs to connect another server in local network.

this is sshfs process list.
[lee <at> adm ~]$ ps aux | grep sshfs
root 2868 0.0 0.0 60344 3812 ? S Sep30 28:20 ssh -x -a
-oClearAllForwardings=yes -oIdentityFile=/root/.ssh/sshfs -2
root <at> staging -s sftp
root 2869 0.1 0.0 625280 4188 ? Ssl Sep30 96:58 sshfs
root <at> staging:/opt/ /opt/
-o IdentityFile=/root/.ssh/sshfs -o allow_other -o uid=48 -o gid=48
root 10108 1.6 0.0 60344 3884 ? S Nov18 23:46 ssh -x -a
-oClearAllForwardings=yes -oIdentityFile=/root/.ssh/sshfs -2
root <at> staging -s sftp
root 10109 2.2 0.1 702568 15604 ? Ssl Nov18 30:55 sshfs
root <at> staging:/opt/
/opt/ -o IdentityFile=/root/.ssh/sshfs -o
allow_other -o uid=48 -o gid=48

webroot mount is always broken(Transport endpoint is not connected) But
View mount is not broken naver(at least nothing)
i used option reconnect and ServerAliveInterval, BUT result is same.
i traced sshfs pid(10108) and log is this.

[lee <at> adm ~]$ sudo strace -p 4887
elect(7, [3 4], [5], NULL, {10, 0}) = 1 (out [5], left {9, 999998})
write(5, "\0\0\0\34e\1l0\2\0\0\0\1\0\0\0\vEnd of file\0\0\0\0"..., 64) = 64
select(7, [3 4], [], NULL, {10, 0}) = 1 (in [4], left {9, 966952})
read(4, "", 16384) = 0
(Continue reading)