[dolphin] [Bug 501118] Copy a large file causes corruption to a network share

[Kevin Dackiw]

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

--- Comment #3 from Kevin Dackiw <kdackiw at gmail.com> ---
I can confirm the addition of cache=none stops the big cache load/flush 
cycle and indeed keeps things steady with the copy.
The target copy did verify correctly.

This was to my file server with SMB multichannel disabled.

Update:  server set to SMB multichannel also is working, and same speed 
as expected.

I tried this before about two months ago and cache=none had no effect, 
so something changed in the meantime :-).  I agree that this seems to be 
a workaround however.

I'm still not 100% sold that it is rock solid and I have been using NFS.
In the meantime, I will go with this being a KDE issue.  How can I help 
to further find the cause of this?

TY!

Kev.

On May 3, 2025 1:35 PM, Jens wrote:
> https://bugs.kde.org/show_bug.cgi?id=501118
>
> Jens<jens-bugs.kde.org at spamfreemail.de> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |jens-bugs.kde.org at spamfreem
>                     |                            |ail.de
>
> --- Comment #2 from Jens<jens-bugs.kde.org at spamfreemail.de> ---
> I can second this, and here is another report:
> https://superuser.com/questions/1814677/files-are-corrupt-after-copying-streaming-them-from-samba-fileshare
>
> Copying using cp, rsync or any other tool on a SMB mount works. Copying via
> Dolphin will corrupt the file.
>
> Workaround: add "cache=none" to the SMB server's mount options so that the file
> copy process is not cached.
> Then, also Dolphin can copy the file without errors. And as an additional bonus
> the copying speed doesn't oscillate so much any more.
>
> This is not a fix however. And I think this is quite a serious issue.
> How can we help finding the root cause of this?
>

-- 
You are receiving this mail because:
You are on the CC list for the bug.