I have the original folder structure where each cloud connection is its own folder. This happened in Google Drive.
I just moved FolderFoo from Google Drive/Folder1/ to Google Drive/Folder2/. Upon moving it, odrive started uploading the entire folder all over again, then marked the original as being in the Trash. It’s a 10GB folder so it’ll take a while to reupload.
Shouldn’t this have just done a move on the cloud? I have seen this behavior in the past, I’m curious if anyone else has.
odrive version 7450
macOS Sequoia 15.2
APFS formatted drive
Hi @nabeards,
Optimized moves are the one soft-spot for the sync engine. Since it is observing filesystem states, it can’t always see the two different actions (disappear from one location and appear in another location) and correlate them as an optimized move. When it doesn’t it will pick it up as an add + delete.
Ideally it will recognize the actions as a single “move”.
Thanks @Tony ! For macOS specifically, seems like fsevents would give the proper notification for a folder being moved vs removed. With slow and limited internet, it took 100 minutes for the resync to finish
Hey @nabeards,
Yeah, I’ve seen that happen too. Moving a folder inside the Google Drive section of odrive ends up re-uploading everything instead of just moving it. Super annoying when the folder is big and the internet is slow. Hopefully, they can make it better at noticing when it’s just a move. Glad you posted it helps to know others are seeing the same thing.
