I launched the command yesterday and it was still running this morning. What I noticed was that it was recopying all the files instead of just copying the new ones.
How is this possible?
The old files have definitely not changed as they are just pictures. The only thing is that they are very large.
Run the command 'rclone version' and share the full output of the command.
rclone v1.66.0
- os/version: Microsoft Windows 11 Pro 23H2 (64 bit)
- os/kernel: 10.0.22631.3296 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.22.1
- go/linking: static
- go/tags: cmount
--no-traverse saves time by not listing all destination. Effectively not checking whether files already exist or not. It makes sense when destination is very large (it takes time to list it) and you copy only few new files.
--no-traverse has the effect of not checking whether the file exists or not. so if it exists he copies it again anyway.
while
--ignore-existing I have the effect of not checking the "content" of the file. so if a file already exists in the destination it doesn't copy it no matter what.
the simple command
rclone copy source:sourcepath dest:destpath
should instead copy only files that are not in dst or that have been modified. To do this does he have to check the MD5SUM every time?
by default differences are detected by testing by size and modification time. To check by checksum you have to force it by providing --checksum flag (assuming that both source and destination support some common checksum mechanism).
run your copy command with -vv (debug output) flag and log will tell you what is happening..