[source]
type = local
[destination]
type = drive
client_id = redacted.apps.googleusercontent.com
client_secret = redacted
scope = drive
token = {"access_token":"redacted","token_type":"Bearer","refresh_token":"redacted","expiry":"2021-08-23T16:44:53.0167204+01:00"}
team_drive = redacted
root_folder_id =
A log from the command with the -vv flag
Not going to include the log here. Main thing is that a file, "aluminium.pdf" exists both in the source, and the destination, yet the dry run log says
2021/08/24 15:33:36 NOTICE: aluminium.pdf: Skipped copy as --dry-run is set (size 1.653Mi)
Skipped copy; surely it should say
Duplicate object found in destination - ignoring
This is happening for many files that exist in both the source in the destination. This is a problem as we're using the comparison between the files moved and the files duplicated to run a report on the 'delta' between the source and destination.
you have duplicates in gdrive, is that the problem?
Negative, we don't have any duplicates in Google Drive. For instance, there is only one "aluminium.pdf" file.
can you post a debug log with the problem; perhaps change the source to point that file?
This is a 90GB+ Drive. Logs would just tell the same story as I did above. Some files are 'checked' and considered not for transfer, some files are 'transferred'. (Obviously this is a dry run so none of this is taking place)
curious why use source:C:\DATA instead of C:\DATA?
We established a local remote source:. It looks like that's not necessary, but it shouldn't change the outcome.
just wanted to be sure you know about rclone check?
Not heard of rclone check - will try to run this command and see if it's useful. There may be an issue that some files have been edited in the destination which it won't consider a 'match' that we need it to consider a match. If the filename is the same, the file is there.
" + path means path was missing on the destination, so only in the source"
i shared my time to post a simple set of commands, two rclone lsf and a rclone copy.
the logs show correct behavior.
to take it a step further, i deleted the dest file and re-ran the rclone copy --ignore-existing.
again, rclone performs the correct action
rclone delete gdrive-a1b2:testfolder01/file.txt -vv
DEBUG : rclone: Version "v1.56.0" starting with parameters ["c:\\data\\rclone\\scripts\\rclone.exe" "delete" "gdrive-a1b2:testfolder01/file.txt" "-vv"]
DEBUG : Creating backend with remote "gdrive-a1b2:testfolder01/file.txt"
DEBUG : Waiting for deletions to finish
INFO : file.txt: Deleted
DEBUG : 4 go routines active
rclone copy C:\data\rclone\scripts\rr\other\newtest\file.txt gdrive-a1b2:testfolder01/file.txt --ignore-existing -vv --dry-run
DEBUG : rclone: Version "v1.56.0" starting with parameters ["c:\\data\\rclone\\scripts\\rclone.exe" "copy" "C:\\data\\rclone\\scripts\\rr\\other\\newtest\\file.txt" "gdrive-a1b2:testfolder01/file.txt" "--ignore-existing" "-vv" "--dry-run"]
DEBUG : Creating backend with remote "C:\\data\\rclone\\scripts\\rr\\other\\newtest\\file.txt"
DEBUG : fs cache: adding new entry for parent of "C:\\data\\rclone\\scripts\\rr\\other\\newtest\\file.txt", "//?/C:/data/rclone/scripts/rr/other/newtest"
DEBUG : Creating backend with remote "gdrive-a1b2:testfolder01/file.txt"
DEBUG : file.txt: Need to transfer - File not found at Destination
NOTICE: file.txt: Skipped copy as --dry-run is set (size 275)
2021/08/24 15:33:36 NOTICE: aluminium.pdf: Skipped copy as --dry-run is set (size 1.653Mi)
imho, either this is human error or a bug with rclone.
without a good set of logs, no way to know....
I guess the examples posted by @asdffdsa are ment to inspire you to pick a single file where you see the issue (E.g. aluminium.pdf) and then check/post the output from these commands