I assume this is a variant of this BUG 334776 it behaves exactly the same Reproducible: Always Steps to Reproduce: 1. mount sshfs 2. try to create a file in that mounted directory Actual Results: Error of "disk is full" appears Expected Results: should create the file
directory mounted through Gigolo which uses gvfs path looks like this: /run/user/1000/gvfs/sftp:host=x.x.x.x,user=root/path/to/dir/ Version 15.08.2 Using: KDE Frameworks 5.15.0 Qt 5.4.2 (built against 5.4.2) The xcb windowing system
KIO version 5.15.0-0ubuntu2
I'm seeing exactly the same thing in Kubuntu 16.04. Any action which results in a file being created/moved/copied to a SSHFS mount results in either a silent failure or a disk full error. Possibly also related to this RAMFS bug: https://bugs.kde.org/show_bug.cgi?id=299156 KIO version 5.18.0-0ubuntu1
Sorry I should have mentioned I'm not using gvfs, I'm using sshfs with afuse but the error is the same. I can delete and open files but not create them or copy them into an sshfs folder.
OK I've been doing some tests and have some additional information.... It ONLY happens when I use afuse not when I use SSHFS directly. For example; if I mount using the sshfs command: sshfs user@server:/ ~/sshfs/user@server/ dolphin ~/sshfs/user@server/ Then Dolphin reports the disk space in the status bar and copy works However if I mount with afuse, for example using: afuse -o mount_template="sshfs %r:/ %m" -o unmount_template="fusermount -u -z %m" ~/sshfs/ dolphin ~/sshfs/user@server/ Then Dolphin states "Unknown size" in the status bar and wont copy. In both situations command line copies work fine. I'm guessing that the fact this problem occurs in gvfs and afuse is related somehow since they are both automounters?
Sorry I should have mentioned in the previous comment that in the first example you will need to create the mount point user@server, in the second its created automatically by afuse.
*** This bug has been marked as a duplicate of bug 344146 ***