How to avoid checksumming 'local' syncs?

[asdffdsa (jojothehumanmonkey)]

@rcRsc

it's pretty obviously an issue with official rclone.

re251sg67nnhm135oad319cpmk/058srvaumm56v2l6q44gc5m8mqujceocescn9putobrv1udqhke0: Modification times differ by 1h59m59.0498134s: 2023-07-05 08:24:09.9501866 +0200 CEST, 2023-07-05 10:24:09 +0200 CEST
re251sg67nnhm135oad319cpmk/058srvaumm56v2l6q44gc5m8mqujceocescn9putobrv1udqhke0: md5 = fc9a1bbf90f7172b148fc8501549c2d7 OK
re251sg67nnhm135oad319cpmk/058srvaumm56v2l6q44gc5m8mqujceocescn9putobrv1udqhke0: Skipped update modification time as --dry-run is set (size 1.271Ki)
re251sg67nnhm135oad319cpmk/058srvaumm56v2l6q44gc5m8mqujceocescn9putobrv1udqhke0: Unchanged skipping

ok, i think this is the issue?

Local Filesystem Unexpected MD5 Calculation

if the sizes are equal and the modtimes are not equal, then what is rclone to do? the flags determine rclone's behavior. i could be wrong, not the first time. let's wait and see what others comment

Local Filesystem Unexpected MD5 Calculation

The thinking behind this logic is this We've detected the file is the same size but has a different modtime. Let's try to avoid an expensive copy by comparing checksums first and if the checksums are the same, just update the modtime. I take your point that on a local -> local copy this is perhaps counterproductive as making checksums for the source and the dest is probably about as expensive as copying the file. This algorithm is explained several times in the rclone docs, but not where an…

might test --size-only
and read about --modify-window

not sure, if and how using --use-server-modtime affects that.
i would pick a single affected file and do some more testing.