Having read different things on dedupe I am unclear exactly how it works so would like to clarify the information.
I am using Google Drive
If deduping based on MD5 is rclone actually removing the duplicate MD5 without using the Google FileID?
Asking because I am sure rclone does not actually generate the MD5 but instead uses the lsf function from Gdrive to get the MD5 values
I am asking because for some odd reason Gdrive is giving me the same MD5 value and the same GDriveID for files with with the same MD5 but located on different TD and also with different time stamps etc
So I just want to clarify if dedupe is actually using the MD5 value and path to dedupe or if it is using the GDriveID
Knowing this will tell me how I have to handle deduping.
2nd Question
Say I have a folder system like this on the same TD
Dir
Dir-A
Dir-B
If I run dedupe on the remote is it going to obtain the MD5 values based on the alphabetical Dir (tree) listing or does it jump around.
When I do move or copy commands I have noticed rclone does not always follow the alphabetical directory folders names, instead it appears to jump around sometimes
My goal is this..
Dir
is the first folder which contains sub folders with the files named as I want them.
Dir-A
Dir-B
etc
contains files which might have had their file names modified, but not the contents.
So my goal is that dedupe would obtain the MD5 from Dir first then recursively delete the matching MD5 in the other Dir(s) in an alphabetical manner.
ie is there a way I guess to make it follow the tree, and only delete the matching MD5 values in other tree's
I hope this makes sense