[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 298976] Dolphin says "no space left on device" instead of overwrite a big file in it.
From:       <ivan.pessotto () gmail ! com>
Date:       2012-05-10 11:40:21
Message-ID: bug-298976-17878-41wVcBAMol () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=298976

--- Comment #3 from ivan.pessotto@gmail.com ---
Ok I understand your reasons, now I tell you mine :)

I'm the user of my PC, so I know what I'm doing when I'm copying a file. If the
destination file already exist, the first thing dolphin must do will be ask to
overwrite or not, and not show an invalid error (IMHO) saying "there's no space
left" when the file will fit to the destination FS.

Then I have 2 choices:
1) If my choose is to "rename" the destination file, then it's right to give me
that error message.
2) If my choice is to "overwrite", then I known I will loose the old existing
file. So if in case of power failure/unplugging the old file is missing, who
cares? I've already choose that file is useless for me.

After a power failure/unplugging I know the copy operation was aborted and the
destination file is inconsistant, but the source file is intact. So the first
thing I will do is reboot/replug and then restart the copy operation. So simple
:)
This is my honest opinion, and I think this is how works "explorer" on windows.

IMHO I don't think working with dolphin can be comparable to tools like rsync.
Dolphin is a file manager, rsync is a file synchronizer and they are used for
different works. Dolphin must be like the 'cp' command.

-----

I don't know if this is a dolphin or kio related issue (or feature if you
like), but I encountered this "bug" using dolphin, if I was wrong, then I'm
sorry.

Thank's anyway and sorry for my english (I'm not good at it).

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]