Fixing KIO copy to USB stick and network filesystems
Comments on “Fixing KIO copy to USB stick and network filesystems”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
KDE's KIO, the layer under Dolphin, now makes copies to USB sticks and network shares finish when data is actually on the device, fixing a 2011 bug (281270) where progress only reflected the page cache. Méven Car's fix uses sync_file_range() with an adaptive writeback window, plus a final flush; moves keep sources until it succeeds. It ships in Frameworks 6.32. The performance figures, such as 1.7-second listings on a 5 MB/s SMB link, are the author's own measurements on one test setup.
Why it ranked
No. 19 of 155 with a score of 0.67. The panel rated it highest on new information (0.95) and technical depth (0.95), lowest on audience breadth (0.48).
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering write-up of a long-standing KIO bug fix with benchmarks, code-level technical depth and measured results; strong substance, niche audience, no overlap with recent stories.
- AI judgeJudge 3gpt-5.6-luna
- A deeply technical, evidence-backed engineering account of fixing long-standing correctness and performance problems in KDE KIO across removable media and network filesystems, with implementation details, benchmarks, and user-visible consequences.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.67total under rubric v2.2
- Significance0.63
- Reader interest0.75
- Audience breadth0.48
- Practical relevance0.68
- Substantiated0.89
- Technical depth0.95
- New information0.95
- Counts against: Promotional0.04
- Counts against: Overclaim0.21
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.60 | 0.60 | 0.68 | 0.63 | 0.08 | +0.24 | +0.150 |
| Reader interest | 0.56 | 0.80 | 0.90 | 0.75 | 0.34 | +0.26 | +0.196 |
| Audience breadth | 0.49 | 0.50 | 0.45 | 0.48 | 0.05 | +0.13 | +0.063 |
| Practical relevance | 0.67 | 0.60 | 0.78 | 0.68 | 0.18 | +0.22 | +0.150 |
| Substantiated | 0.89 | 0.85 | 0.92 | 0.89 | 0.07 | +0.05 | +0.044 |
| Technical depth | 0.99 | 0.90 | 0.95 | 0.95 | 0.09 | +0.05 | +0.047 |
| New information | 0.92 | 0.95 | 0.98 | 0.95 | 0.06 | +0.05 | +0.048 |
| Promotional | 0.04 | 0.05 | 0.02 | 0.04 | 0.03 | −0.19 | −0.007 |
| Overclaim | 0.40 | 0.15 | 0.08 | 0.21 | 0.32 | −0.11 | −0.023 |
| Sum of contributions | +0.668 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.668 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-28/19/"><img src="https://rubric.hrih.si/badge/2026-10-28/19.svg" alt="Ranked #19 on Rubric, 28 Oct 2026" width="245" height="28"></a>Claim check
Claim check: 2 matches source · 4 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceDate
The changes are merged and will be in KDE Frameworks 6.32, released November 13th 2026.
The cited source says the same thing.
The article says “All of it is merged, and will be in KDE Frameworks 6.32, released November 13th 2026”
The source says “6.32 | (expected) Fri November 6, 2026 | (expected) Fri November 13, 2026”
Source cited by the article: community.kde.org/Schedules/Frameworks
Couldn’t checkDate
Bug 281270 was opened in September 2011 against KDE 4.7, reporting that copy speed and progress to a removable disk reflect the local cache rather than the disk.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “In September 2011, against KDE 4.7, someone opened bug 281270”
The source says No passage could be compared.
Source cited by the article: bugs.kde.org/show_bug.cgi
Matches sourceNumber
MR 2326, in KIO 6.30, caches mounts by the mount id from statx() and made a lookup by id about 700 times faster.
The cited source says the same thing.
The article says “A lookup by id became about 700 times faster”
The source says “A microbenchmark of repeated lookups on one mount shows about 700x for the by-id lookup and 170x for the by-path lookup”
Source cited by the article: invent.kde.org/frameworks/kio/-/merge_requests/2326
Couldn’t checkNumber
MR 2487 reads a missing mount with statmount(), so a lookup with an unresponsive network server went from more than 15 seconds to about 1 ms.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “the lookup went from more than 15 seconds to about 1 ms”
The source says No passage could be compared.
Source cited by the article: invent.kde.org/frameworks/kio/-/merge_requests/2487
No source givenNumber
On SMB with default cache=strict, almost every listing during a 1 GiB copy over a 5 MB/s link waited 15 to 20 seconds.
The article gives no link or citation for it.
The article says “Over a 5 MB/s link, almost every listing during a 1 GiB copy waited 15 to 20 seconds”
The source says No source to compare with.
No source givenNumber
With the writeback window, a whole folder listing took 1.7 seconds on the 5 MB/s link instead of 5 to 11 seconds.
The article gives no link or citation for it.
The article says “a whole listing took 1.7 seconds on the 5 MB/s link instead of 5 to 11”
The source says No source to compare with.
No source givenNumber
An fsync() per file made copying 3000 files of 16 KiB take 10 seconds instead of 0.04 seconds on a local disk.
The article gives no link or citation for it.
The article says “made 3000 files of 16 KiB take 10 seconds instead of 0.04 seconds on a local disk”
The source says No source to compare with.
No source givenVersion
Linux 5.19 changed copy_file_range() so that it fails with EXDEV between two filesystems again.
The article gives no link or citation for it.
The article says “Linux 5.19 changed that back: between two filesystems, the call fails again with EXDEV”
The source says No source to compare with.
Also covered by
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.