Version: (using KDE KDE 3.5.8) Installed from: SuSE RPMs Currently two cases are reported as one: * when there is not free space left on disk * when it is impossible to create new file KDE handles that as "no free space", so for example when I want to delete file and there is (2) case -- I see message with looks really bizarre -- 300MB free space, and I cannot trash a file ;-) Please make a distinction between those two cases.
the kernel makes no distinction between the two cases when reporting the error. kde would have to apply some heuristics to figure it out, but that's never going to be reliable. so this is WONTFIX, as far as i'm concerned. use a modern file system that dynamically allocates inodes.
> the kernel makes no distinction between the two cases when reporting the > error. kde would have to apply some heuristics to figure it out, One extra call to get free space info? If I (as a user) can figure it out but simply calling kwikdisk KDE could do the analogous thing for users sake. > use a modern file system that dynamically allocates inodes. Hmm, quoting "ReiserFS (...) Another benefit lies in the dynamic allocation of inodes." http://www.novell.com/documentation/suse91/suselinux-adminguide/html/apas02.html I had 300MB space on disk and I couldn't trash 0B files and KDE (or trash?) said that there is no room to create .trashcan info file. You can say that maybe reiserfs is not modern enough, but there would always be a limit for some resource, so it is better to improve that information dialog.
> but there would always be a limit for some resource > yes, exactly. and you'll never know what it is. there is no standard way to differentiate the reasons, so there is no way to know what exactly went wrong. the user is in the best position to find out, as he knows the system's setup. one could add some common reasons (out of inodes, over quota, etc.) to the error message, but that's about it.
> there is no standard way to differentiate the reasons, But when you are in trouble you know what to check -- step after step. So there is an algorithm -- it is not perfect because it is hard to anticipate what can go wrong, however now we know at least two steps for sure. Why not add them to KDE to all benefit?
Disk allocation reported as 128TiB, 140,737,468,347,000 bytes, whole hard drive is less than 500GB. 20GB drive partition reported full again, chronic problem. System problem, I do not store files on this partition. Can no longer upgrade my system, just get errors.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
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 mark the bug 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!
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!