Copying files to a sshfs share fails with the error: Could not write disk full. This appears to occur because the actual disk usage is not transmitted by sshfs, so to dolphin, it appears that the disk has 0 bytes available. Nautilus has a workaround for this, and using the fish: protocol mostly works (always get the warning that user details were unable to be assigned). But these are clunky workarounds, requiring a different program (nautilus is not part of the KDS ecosystem and is a GTK app) or fish which has many limitations that the persistent file solution sshfs overcomes.
I can copy to sshfs just fine. How are you creating the file system?
I am using autofs and my auto.ssh-shares file looks like this: <MYDIR> -fstype=fuse, port=XX, rw, nodev, nonempty, noatime, allow_other, max_read=65536, IdentityFile=/home/XXX/.ssh/id_rsa :sshfs\#MYNAME@XX.XX.XX.XX\:/home/XXX/YYYY/
Does it work if you just use: sshfs user@host:/remote/path /local/path
No I get an access denied error in that case. Using autofs, I get could not write: disk full
I should have mentioned that using the CL sshfs, I could see and open files, and in both cases other applications can write to the share. I only have this problem in Dolphin.
Does "other applications" also include another KDE application? The problem might be a bug in KIO, but I am not sure if that is correct as you should then be able to access the share with sshfs. @Elvis, do you have an idea where this issue could originate from?
>Does "other applications" also include another KDE application? Sort of. I just opened a pdf file from my share with okular and then saved it back to the same share with a new name. It opened with no problem, but when I saved it I got an error message popup. "Could not change permissions for <full file name with path> But, it DID save the file under the new name. With Dolphin I get a notification 'Could not write, disk full' inside of the dolphin window and it won't write to the destination. GTK applications (Nautilus, LibreOffice) don't behave this way, so KIO might indeed be the issue?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!