I have the same file in my unencrypted and encrypted drives. I moved both files to a new directory and renamed both files to match each other in the hopes of not having to reupload the same file to my encrypted drive. Now, whenever I run the copy command, Rclone still tries to copy over the same file. I'm guessing the md5sum changed so it's not registering as the same file?
Is there any way to duplicate the md5sum of the original file to match the file in the encrypted drive so Rclone stops trying to copy over the exact copy?
What is your rclone version (output from rclone version)
v1.57.0
Which cloud storage system are you using? (eg Google Drive)
Google Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
note: cannot mix crypted and non-crypted files in the same dir.
when you run the command, rclone will crypt the source files from gdrive: and copy them to gdrivecrypt:
rclone will save the source file md5 hash as metadata in the dest file.
rclone will not re-sync a source file unless it has changed.
if you would use a debug log, you can see what rclone is doing
add -vv to the command. would see something like
rclone sync gdrive:source gcrypt:dest -vv
DEBUG : file.txt: md5 = f0d751816d3dc5a6675e1ba22e68d82e OK
INFO : file.txt: Copied (new)
rclone cryptcheck gdrive:source gcrypt:dest -vv
INFO : Using md5 for hash comparisons
DEBUG : file.txt: OK
NOTICE: Encrypted drive 'gcrypt:dest': 0 differences found
NOTICE: Encrypted drive 'gcrypt:dest': 1 matching files
Modification times differ by -12.741s: 2018-06-16 22:23:59.741 +0000 UTC, 2018-06-16 22:23:47 +0000 UTC
Not even sure how that happened, as it was 3 years ago. I then ran the code with --checksum and that lets me run the copy command without overwriting the existing file. To fully fix the issue, I'm trying to change the metadata of the files so they match up. Thanks guys.