When using Dolphin to copy, move or create files into a directory where a ramfs volume is mounted, it refuses with the error, "Could not write file . Disk full." It seems Dolphin is checking the available free space before writing, but a ramfs doesn't have a fixed size - you can keep writing to it until you run out of RAM - and consequently Dolphin is never satisfied. Reproducible: Always Steps to Reproduce: # mkdir ramfs # mount -tramfs RAMDISK ramfs/ # chmod 777 ramfs/ Use Dolphin to copy or move a file into the ramfs directory. Actual Results: File is not copied; error message "Could not write file . Disk full." The problem didn't exist in previous versions.
Git commit af114cc90c4767012923d6d3901c6fbf7b813ea2 by Dawit Alemayehu. Committed on 21/06/2013 at 01:15. Pushed by adawit into branch 'master'. Allow KIO to copy/move files to ramfs mounts. REVIEW: 111115 FIXED-IN: 4.11 M +9 -0 kdecore/io/kfilesystemtype_p.cpp M +1 -0 kdecore/io/kfilesystemtype_p.h M +1 -1 kio/kio/copyjob.cpp http://commits.kde.org/kdelibs/af114cc90c4767012923d6d3901c6fbf7b813ea2
This is broken again. Dolphin version 18.08.0. "There is not enough space on the disk to write". Not a permissions issue -- the mount is writable and manageable from other programs and file managers.
I'm sorry we weren't able to get to this yet. Is this still an issue with Dolphin 24.12.3 or greater?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.