Bug 501118 - Copy a large file causes corruption to a network share
Summary: Copy a large file causes corruption to a network share
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.12.2
Platform: Manjaro Linux
: NOR grave
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-05 20:47 UTC by Kevin Dackiw
Modified: 2025-03-05 21:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Dackiw 2025-03-05 20:47:07 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
Large file copies corrupt the target copy.

STEPS TO REPRODUCE
1.  Copy a large (in my case a 10G file) to a fstab mounted CIFS share
2.  Check integrity of copied file.  A CRC comparision or archive with a check will show a failed copy.
3.  Note that this does not happen with Krusader, PCManFM, or even a 'cp' between the two paths.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Kevin Dackiw 2025-03-05 21:10:23 UTC
Tested with NFS and no corruption.  Dolphin through a KIO slave is ok too.  I've noticed that the copy through a CIFS mount via fstab is buffering almost the whole copy into RAM then pushing it through.  Perhaps some kind of background memory issue with that route.

Checked RAM sticks and tested.  Swapped RAM too.  It's only that copy path.  I can use KIO for a bit until things settle with other parts and discuss over at the discuss area :-)