![\"A](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/usb-before.svg\")
Méven Car · KDE Blogs · October 27, 2026
\nI am going to tell the story of fixing a very high priority bug that was 15 years old. Arguably the worst KIO bug.
\nIn September 2011, against KDE 4.7, someone opened bug\n281270: "When copying files to a removable disk,\nspeed and progress reflect copying to the local cache not to the disk itself". The report notes\nthe copy notification showed about 50 MB/s to a USB 1.1 device, which cannot go faster than\n12 Mbit/s. The reporter had asked a kernel developer, Alan Stern, what was going on, and summed up\nhis answer:
\n\nit shows that the copying operation is finished when it has not even been started.
Seventy-seven comments and 17 duplicates later, that is still how a copy to a USB stick behaves in the\ncurrent release of KIO. My last post\nabout copying was about making KIO copy faster.\nThis one is about the opposite case, a destination that is slower than KIO, and about making the\nprogress bar and copy completion accurate.
\nThe changes are in four KIO merge requests:\nMR 2506 finds out which devices are\nremovable, MR 2517 and\nMR 2518 flush the device at the end of\na copy or a move, and MR 2283 adds the\nwriteback window. All of it is merged, and will be in KDE Frameworks 6.32, released November 13th 2026.
\nWe will see the cause of the bug, its history, and what it took to fix it.
\nThe file worker copies a file by handing its data to write(). write() returns as soon as the\ndata is in the page cache, in memory. The kernel writes it to the device later, when it decides to.\nOn a local SSD, later means very soon, and you never notice. On a USB 2.0 stick that writes at\n2.3 MB/s, it is another story. Here is a 128 MiB file:
For more than a minute, Dolphin considers the copy finished while the stick is still writing. The\nprogress bar was showing how fast KIO filled memory. Pull the stick out during that minute, and your\ndata is gone.
\nNetwork filesystems have a different symptom from the same cause. A large copy to an NFS or SMB\nshare leaves hundreds of MiB in memory to send to the server, and the progress runs far ahead of\nit. On SMB it is worse than a wrong number: with the default cache=strict, looking at a file\nwaits until its dirty data is written. Listing the folder you are copying into looks at that file.\nOver a 5 MB/s link, almost every listing during a 1 GiB copy waited 15 to 20 seconds.
The right tool actually showed up very early. Two days after the report, Christoph Feck asked whether there was a\nway to learn when the data is really on the disk "without causing massive slow downs that any sync\ntype calls would cause". Two weeks later, the reporter passed on Alan Stern's answer,\nsync_file_range(), and Christoph replied that it looked like "exactly what we need". That was\nSeptember 2011, and it is the call KIO now uses.
Then not much happened for years, apart from users confirming it and seventeen duplicates. In 2021, Nate\nGraham raised it to the highest priority, because a move deletes the source files while the copies\nare still in memory. In 2022, he changed the Disks & Devices applet, so that ejecting a device\nexplains that it is still writing. In 2024, Christoph tested the cachestat() call of Linux 6.5,\nwhich reports how much of a file is still dirty in memory, but only for one file at a time.
This bug has been my white whale. I have been contributing to KIO since 2018, and I am still learning\nhow the Linux storage stack behaves underneath it. I tried twice in 2024 and did not get\nsync_file_range() right. In MR 1718,\nthe sync_file_range() path stayed commented out. In KIO\nMR 1764 and Dolphin\nMR 862, the worker waited for the\nwriteback of the chunk it had just written, which had not started, so it never waited at all. Waiting\nfor the window before the one just written is what makes it work. I didn't spot the issue, nor any\nreviewer unfortunately.
Since then, another contributor proposed turning off the cache for copies, in\nMR 2162, which was closed.
\nMaking the copy correct is the easy part: call fsync() after every file, or open the destination with\nO_DIRECT and skip the cache. Both make copies several times slower, and they would slow down\nthe fast local disks too, where nothing was wrong. Making it\ncorrect without making it slow is what took fifteen years, and it needed several things that were\nnot there before.
A way to wait for part of a file. POSIX only offers fsync(), which waits for everything.
sync_file_range() is Linux only, and its own manual calls it "extremely dangerous": it does not\nwrite the file's metadata, so on its own it guarantees nothing after a crash. It can bound how\nmuch is in memory, but the end of the copy still needs a real flush.
Knowing which destinations need it, without asking them. The filesystem type does not show
whether a device can be unplugged, and asking a network filesystem anything is a round trip to a\nserver that may be slow. KIO reads the answer from the\nmount table and from sysfs instead, and two earlier changes to KMountPoint made that cheap\nenough to do for every copied file:
MR 2326, in KIO 6.30, caches
mounts by the mount id that statx() returns since Linux 6.8, instead of parsing\n/proc/self/mountinfo on every lookup. A lookup by id became about 700 times faster.
MR 2487, in KIO 6.32, reads a
missing mount with statmount(), which does not walk any path, so a network server that does\nnot answer no longer blocks the lookup. In that case, the lookup went from more than 15 seconds\nto about 1 ms.
A place to flush at the end of a copy. The file worker copies one file per command, in its own
process, and never knows which file is the last one. Only the CopyJob, in the application, knows\nwhen the whole copy is over. So the flush needed a new worker command, and a way for the worker to\nnotify the job that a flush is needed. On the way, I found that FileCopyJob dropped the metadata\nthat the worker sent with a copy, so the CopyJob could never have seen it.
A window size that fits every destination. A window too small slows a fast link, and a window
too large never fills on a slow one. That is why it now adapts, and why the progress has to stay\nmonotonic when the window shrinks.
Waiting for the device after every write would be correct but very slow. Waiting only at the end\nleaves the progress wrong for the whole copy. KIO now does something in between, with\nsync_file_range(), which lets a program start the writeback of part of a file and wait for it.
The data is written in windows. When a window is full, the worker hands it to a helper thread,\nwhich writes it back and waits for it, while the copy fills the next window. The copy only waits\nwhen the window before the one it hands over is not written yet. So at most two windows of the copy\nare ever in memory and not on the device, and the progress bar is never more than one window ahead\nof what is really written.
\nThe helper thread was needed to accommodate CIFS, the kernel client for Samba and Windows shares. On CIFS,\nthe call that starts the writeback of a window does more than start it: it sends the data to the\nserver, and waits for the server to grant the credits to do so, blocking the calling thread for about 157 ms per 128 MiB window.\nSo the copy could not fill the next window while the previous one was sent. With the helper thread making that call, sending a window and\nfilling the next one overlap.
\nA window holds about 200 ms of writeback, at the speed measured on the window before. It starts at\n1 MiB, can at most double from one window to the next, and stays below 16 MiB, or 128 MiB on CIFS.\nOn a fast link the windows grow, so the copy keeps its speed. On a slow link they stay at about\n1 MiB, and anything that has to wait for the file waits a fraction of a second, not for the whole\nfile.
\nA window bounds how much is left in memory, but there is still something left at the end. For a\nremovable device, KIO now also makes the end of the copy wait for it.
\nA file larger than the largest window, 16 MiB, is flushed with fsync(), and then its folder, before\nthe copy reports it done. By then the window has already written all but the last two windows, so the flush is\nshort.
Small files are the hard part. The obvious fix, an fsync() for every file, made 3000 files of\n16 KiB take 10 seconds instead of 0.04 seconds on a local disk. So the worker flushes no small file\nby itself. After a copy to a removable device, it notifies the job, and the CopyJob sends it one\nmore command before reporting success: write back the whole filesystem of the destination, with\none syncfs(). While that runs, the copy notification shows "Writing the copied data to the device...".\nIf the flush fails, the copy fails, because the data may not be on the device.
A move needed more than that. Before, KIO deleted each source file right after its copy, while\nthe copy could still be only in memory, which is why the bug got its highest priority. Now a move to\na removable device keeps its sources until the flush has succeeded, and deletes them after it. If the\nflush fails, or the stick is unplugged during it, every source stays. A source that changed while it\nwaited for the flush stays too, with a warning. A copy or a move that stops on an error, or that you\ncancel, still flushes the device, and a move then deletes only the sources of the files that are on\nit.
\nHere is the same USB stick again, with the small files added:
\n![\"Copies](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/usb.svg\")
Yes, the copies now take longer by the clock, but only because the clock now includes the time the\nstick spends writing. The time until the data is really on the stick did not get worse. The speed of this stick\nvaries a lot from run to run, so the 28 seconds against 68 to 91 seconds for the large file is not a\nspeedup I would count on. The small files never fill a window, so they only depend on the flush at\nthe end.
\nA local fixed disk does not need any of this, and keeps the current behaviour exactly. With the\nremovable policy forced onto a local disk for testing, the 3000 small files took 1.55 s against\n1.54 s before the change.
\nDeciding what is removable is less obvious than it sounds. The filesystem type does not expose it: exFAT\ncan be a memory card, and FAT is also the EFI partition of your laptop. Most USB disks do not even\nreport removable media. MR 2506 adds a private function to KIO that asks sysfs: the disk's own\nremovable flag, then the USB port or PCIe slot it hangs off, which the kernel marks removable when\nit can be reached from outside the machine, and SD cards. It follows encrypted and LVM volumes down\nto the disk under them.
\nNetwork filesystems are easier: every mount that KIO already considers slow gets a window. That is\nNFS and CIFS, but also Ceph, GlusterFS, 9p, sshfs, and FUSE filesystems such as rclone. The worker\nfinds the mount from the mount id of the destination folder, without a round trip to the server.
\nTo measure this, I used KIO's own copy job, comparing KIO master just before the change with KIO\nmaster after it, while another thread listed the destination folder every 50 ms. The SMB server ran on the same machine, with 2 ms of\ndelay added to its traffic, and for the slow link a limit of 40 Mbit/s, about 5 MB/s.
\nOn the slow link, the listing is the difference you would feel:
\n![\"Listing](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/smb-listing.svg\")
![\"Copy](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/smb-slow.svg\")
The copy runs about 3% slower with the window. On a fast link, the copy keeps up:
\n![\"Copy](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/smb-fast.svg\")
One of the five copies before the change failed with a write error from the share, so these\nnumbers come from four rounds. The times vary between runs: in an earlier run, the copy with the\nwindow was 4% slower.
\nGetting there took me four tries. My first version was 10 to 20% slower on the fast link, because\nof the CIFS behaviour described above. Then, with the windows aimed at 500 ms, listings on the slow\nlink went up to 4.2 seconds, because each request of a listing waits behind the window being sent.\nAiming the windows at 200 ms brought the listings down to 1.7 seconds.
\nNFS, on the same machine with 2 ms of delay:
\n![\"Copy](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/nfs.svg\")
The copy times are close: 11% slower in the first round, and slightly faster in the two others.
\nBug 423187 collects many ways in which a slow mount\ncan freeze Dolphin. In one of its comments, Frank Gehann copied a 100 MB file to an SMB share while\nbrowsing it, and found two causes: Dolphin's main thread waiting for answers from the share, and\nfolder listings waiting behind the queued upload.
\nThe window helps with the second cause: each request of a listing now waits behind at most two\nwindows, about 400 ms of writeback, and a whole listing took 1.7 seconds on the 5 MB/s link instead\nof 5 to 11. The statmount() change\nhelps with part of the first one. KFileItem::isSlow(), which Dolphin calls on its main thread\nbefore it reads a file to find its type, no longer waits for any server, on Linux 6.8 or later. Work is underway to fix the\nrest of the first cause in Frank's open\nMR 2484 and\nMR 2485.
One measurement sent me down a rabbit hole. During a large copy to the USB stick, listing a folder on\nthe stick sometimes took about 15 seconds, before the change as much as after it. It looked like the\nwriteback window was making something wait.
\nIt was the stick. Roughly every 8 seconds, a single 120 KiB write to it took 4 to 7 seconds to\ncomplete, and the listing waited for a page that was stuck behind such a write. KIO cannot fix a\ndevice that stops for seconds at a time, but at least we now know the copy is not to blame. In the runs for this post, the\nslowest listing took 3.6 ms during the copy of the large file, but 7 seconds during the copy of the\nsmall files, against 15 seconds before the change.
\nOne more thing landed along the way, and this one is a plain speedup. In 2021, in Frameworks 5.88, I replaced sendfile() with\ncopy_file_range() in the file worker, in\nMR 602. At the time, Linux copied with copy_file_range() across\nfilesystems too. Linux 5.19 changed that back: between two filesystems, the call fails again with\nEXDEV. Since then, a copy from one filesystem to another went through read() and write() in the\nworker, one buffer at a time.
MR 2520 now falls back to\nsendfile() in that case, which copies from one file to another inside the kernel:
![\"Copy](\"https://blogs.kde.org/2026/10/27/fixing-kio-copy-to-usb-stick-and-network-filesystems/sendfile.svg\")
A copy to the USB stick takes as long as before, because its write\nspeed is the limit. This one is merged too, and will also be in KDE Frameworks 6.32.
\nWith all this, a copy to a USB stick now finishes when the data is actually on the stick.\nOn network filesystems, the progress now follows what the server has received, and the share stays\nusable during the copy.
\nsync_file_range() is mainly used by databases and storage engines. No other file manager that I\nknow of uses it. Now KIO, and so Dolphin, uses it too.
Happy unplugging.
\nOriginally published at KDE Blogs.
","headings":[{"level":2,"text":"Why a copy finishes before it has started","id":"why-a-copy-finishes-before-it-has-started"},{"level":2,"text":"Fifteen years in one bug report","id":"fifteen-years-in-one-bug-report"},{"level":2,"text":"Why it took so long","id":"why-it-took-so-long"},{"level":2,"text":"A writeback window","id":"a-writeback-window"},{"level":2,"text":"Complete means on the device","id":"complete-means-on-the-device"},{"level":2,"text":"Which destinations get a window","id":"which-destinations-get-a-window"},{"level":2,"text":"Numbers on network shares","id":"numbers-on-network-shares"},{"level":2,"text":"Part of a frozen Dolphin","id":"part-of-a-frozen-dolphin"},{"level":2,"text":"The stick that pauses","id":"the-stick-that-pauses"},{"level":2,"text":"Copying between two filesystems","id":"copying-between-two-filesystems"},{"level":2,"text":"Closing","id":"closing"}]}}