Bug 299156

Summary: Dolphin won't copy files to a ramfs - it thinks the disk is full
Product: [Unmaintained] kio Reporter: FreshlyToe
Component: generalAssignee: David Faure <faure>
Status: REOPENED ---    
Severity: normal CC: adawit, g507839, joao.vidal.silva
Priority: NOR    
Version: 4.8   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: http://commits.kde.org/kdelibs/af114cc90c4767012923d6d3901c6fbf7b813ea2 Version Fixed In: 4.11
Sentry Crash Report:

Description FreshlyToe 2012-05-01 09:59:04 UTC 
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.
Comment 1 Dawit Alemayehu 2013-06-21 21:46:05 UTC 
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
Comment 2 g507839 2021-09-07 03:20:23 UTC 
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.