FreeFileSync Forum

I came here to report the same bug, As best I can tell what is happening is I have multiple computers trying to update the file at the same time and google drive is making duplicate copies. Google drive stores files in a weird way and so having multiple files with the same name is technically ...

I would 100% be ok with setting a sync rule that just says if duplicate files exist that are older just nuke both and upload new file.

This might be good enough for you, but it isn't good enough as a general rule. Just picking one of a set of equally-named files is like gambling with files ...

https://rclone.org/commands/rclone_dedupe/

Can something akin to this be integrated or implemented into the program?

"--dedupe-mode newest - removes identical files then keeps the newest one."

None of these suggestions work because Google Drive does not offer transactional file creation. There's just a gap between checking if a file exists, and creating a new one. It's a race condition by Google's design.


You are focusing on the preventing it happening part.
While some suggestions ...

I was hoping this would be fixed by now but it has persisted for well over 15 versions.


There is nothing to fix here. The behavior is exactly as Google wants it to be: https://webapps.stackexchange.com/questions/144039/google-drive-weirdly-allow-files-folder-with-the-same-name-in-the-same ...

I came here to report the same bug, As best I can tell what is happening is I have multiple computers trying to update the file at the same time and google drive is making duplicate copies. Google drive stores files in a weird way and so having multiple files with the same name is technically ...