https://bugs.kde.org/show_bug.cgi?id=419266
Davide Gianforte <dav...@gengisdave.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
CC| |dav...@gengisdave.org
Resolution|--- |NOT A BUG
--- Comment #1 from Davide Gianforte <dav...@gengisdave.org> ---
In Linux, file copies (really, all files) are handled through a memory buffer.
When you start a copy, you should see a fast progress because it is filling the
buffer and when it is filled, the real write starts.
Using a system monitor (e.g. KSysGuard, htop) you can see a memory drop when
the copy ends, meaning that the buffer was freed. For the same reason, if you
copy a file over a network share you also see that the traffic starts a bit
after. Almost all systems, like KIO which is used by Krusader, show the
percentage of data sent to the buffer and it seems that the copy stucks at 100%
because the buffer size is yet to be written on disk.
--
You are receiving this mail because:
You are watching all bug changes.
