Consistently getting "corrupted on transfer: sizes differ" syncing to an SMB share

[yichi_yang]

@asdffdsa

this is the root of confusion.
believe me, for a write-protected, read-only vss snapshot, that is a more than a valid assumption.
in my humble opinion, not a valid conclusion.

Thank you for the clarification. I think I see your point now. I'll do a bit more testing with other copy tools over the weekend.

Do you agree we indeed have the same problem (I'm referring to the one you reported here)?

`rclone copy t:\ --include=filename` does NOT work, but `rclone copy t:\filename` works

What is the problem you are having with rclone? rclone copy displays different behavior depending on how the source is specified. rclone will copy the source file rclone copy t:\filename rclone will NOT copy the source file rclone copy t:\ --include=filename note: from the log below, size changed from 1147752 to 1213336 the correct filesize is 1147752 Run the command 'rclone version' and share the full output of the command. rclone version rclone v1.64.0 - os/version: Microsoft Wind…

Note I only run into problem when I try to rclone sync --filter-from:

@yichi_yang

As there are too many files in the user folder, I pasted below the logs without the -vv flag. Note these files cause corrupted on transfer: sizes differ every time.

But if I directly rclone sync \path\to\problematic_file, it works without problem:

@yichi_yang

I tried to sync one of the offending files with -vv, but interestingly that works without issue.

(I might have missed it, but) when you mentioned rclone copy t:\ --include=filename in that other post, I think it behaves the same as your test above if you add --local-no-check-updated, correct?

@asdffdsa

file sizes of the copied files