I should have reviewed the forums where someone had a similar situation and did a de-authorization and then re-authorization and now odrive is populated with the placeholders as expected.
I am going to proceed to perform an rsync with a local machine so that I can get the latest versions of the cloud sync’d folders without having to pull them remotely.
It also looks like since I restored, that odd problem where folders outside of odrive not longer had the odrive commands (like “Sync”, for starters) so that’s a plus. That should make syncing my local copies of the folders which are already fully synced (once odrive verifies they are all the same files of course) but I have one thing to confirm-
When I have a complete copy of an entire cloud store, like a Google Drive for instance on my local filesystem, when I command odrive to sync to the matching cloud share in odrive, as long as that top level share folder name matches the local copy, it will verify the files are in sync and maintain the sync… not make a copy of the folder inside that share?
For example, say the top level folder of my Google Drive as it appears in the odrive folder is called “I_Hate_Sand”. From this new computer which lacks the cloud syncd folders, I then rsync the same folder from another machine on my LAN that also has a synced copy of “I_Hate_Sand” using rsync in archive mode therefore preserving all file properties, such as permissions, ownership, last modified date, etc… Once this copy of the folder “I_Hate_Sand” is complete so there is a local version of the same folder on the new computer, just static, unlinked, and unsynced , it’s now ostensibly the same folder “I_Hate_Sand” as it appears on both on that other computer which I copied it from, as well as what’s in Google Drive form the top level down, and it bears the same name in ordrive s list of shares as “I_Hate_Sand”. Then, in order to sync the static version of “I_Hate_Sand” with the Google Drive which is called “I_Hate_Sand” in odrive’s list of shares, I select “Sync to odrive” command in Finder in the context of that local copy of “I_Hate_Sand” so that it will sync with odrive to the location “/I_Hate_Sand” as the “Storage Location” in the odrive Web GUI, will odrive smartly see that it is the same folder and then traverse the file hierarchy, syncing any discrepancies (which there shouldn’t be, assuming no changes were made during this process) and therefore avoid any needless copying over the internet- just ensuring the files are in fact all the sync and will then keep them in sync going forward? Or Will it dumbly create a new folder on Google Drive called “/I_Hate_Sand/I_Hate_Sand” and proceed to upload the entire contents of the folder to Google Drive, effectively duplicating the entire file hierarchy? Asking for a friend.
Sorry for the painfully explicit language, but I don’t want there to be any confusion about what I am trying to do.
Thanks,