Uh oh. The run did find about 15 pairs of legitimate duplicates that it removed. However it also fully deleted 2 large folders of photos from Google Drive! Here's the head of the log file:
2020/04/18 21:39:57 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone" "--log-file" "/Volumes/Google/2020-04-18-dedup-GDriveGPhotos.txt" "-vv" "--dedupe-mode" "rename" "dedupe" "gdrive:/GDriveGPhotos"]
2020/04/18 21:39:57 DEBUG : Using config file from "/Users/username/.config/rclone/rclone.conf"
2020/04/18 21:39:57 DEBUG : gdrive: Loaded invalid token from config file - ignoring
2020/04/18 21:39:57 DEBUG : gdrive: Saved new token in config file
2020/04/18 21:39:58 INFO : Google drive root 'GDriveGPhotos': Looking for duplicates using rename mode.
2020/04/18 21:41:57 INFO : 2012b: Merging contents of duplicate directories
2020/04/18 21:41:58 INFO : 2012b: merging "2012-11-05"
2020/04/18 21:41:59 INFO : 2012b: merging "2012-11-10"
2020/04/18 21:41:59 INFO : 2012b: merging "2012-11-30"
2020/04/18 21:42:00 INFO : 2012b: merging "2012-11-18"
2020/04/18 21:42:00 INFO : 2012b: merging "2012-11-03"
This continues, iterating through every day in the 2012b and 2013b folders. At the end of the run, neither folder is present in Google Drive anymore.
I suspect this is because these folders are originally in my Google Backup and Sync folders, where I selected the add this folder to Google Drive and it showed up under Google Drive. I note that the folders are no longer under Google Backup and Sync anymore either.
In my particular situation I'm OK as I have copies of these files elsewhere, but obviously the above behavior is destructive on the Google Drive side in a way that I don't think fits the usual semantic interpretation of "deduplication".
This is purely speculation on my part, but if the way the "add this folder to Google Drive" functions is by placing aliases in Google Drive, and those aliases are all small file pointers of the same file size, maybe they were considered duplicates and thus merged?
Please let me know how to proceed, including whether I should file a ticket in the repo. Also LMK if forum etiquette is to migrate this to a new thread since this is a separate issue from my original post.
I should also highlight that I "added" these Google Backup and Sync folders to Google Drive before the recent conversion to the shortcuts model. The menu option I used (wording was something like "add this folder to Google Drive") is no longer available, and has been replaced with an "Add Shortcut to Drive" menu item.
I ran a quick test with a simple folder of files uploaded to Google Backup and Sync, and then added as an alias to Google Drive. The problem doesn't seem to manifest itself because rclone complains that the Failed to dedupe: find duplicate dirs: directory not found.
Backups are great! Google Drive's trashcan might be all you need though. I would be very wary of the Google Drive dedupe in rclone 1.51. Maybe wait for the next version, or downgrade if you need to run dedupe now.
@calisro, I was routinely running rclone dedupe across my Google Drive whenever rclone sync identified duplicates and encountered issues with 1.51.0
One issue was the sudden deletion of many files with complex identities in terms of being in multiple folders, not just duplicates in the same folder. My understanding is that the glitch leading to his arose in 1.51and has now been fixed.
Again, in my own case I had backups and the Google Drive trashcan, but have suspended using dedupe until the next release.
Thanks!. I see. I'm running the beta so it's "fixed" there. @felciano anyway to recreate your issue and see if it is also fixed in the beta? I see you're running the last release instead. I wonder if you ran into the same issue.