#Mac trash folder cannot be emptied upgrade#
#Mac trash folder cannot be emptied download#

I just attempted to delete a file from the trash by right clicking it, it asks if I want to restore or delete - I select delete, A few seconds later I get the “you have restored this file, but you do not have edit permissions.”

#Mac trash folder cannot be emptied upgrade#

It looks to me as if I will not get this resolved unless I upgrade my subscription? I am the owner of the files and the folders. If you uninstall odrive, the data will remain in the cloud and the data locally will remain as it exists at the time of uninstall, but they will not longer be linked, of course. If those copies are changed locally, then odrive will sync those changes back to the cloud, etc…

#Mac trash folder cannot be emptied download#

You can then download those files/folders, if you wish, to create a copy of the data on your local machine. These represent your cloud data without taking up space on your system. You probably noticed that odrive started out with all placeholder files (.cloud and. It also give you the opportunity to sync down (download) files from the cloud. If the files that are throwing the permission’s error are owned by you, then this may be a different issue (unless they are inside a folder that you do not own and have removed write permissions, for example).įor syncing, odrive will sync any new or changed files that you place into the odrive folder to the cloud. I was using “Shared With Me” as a reference point, but you can have files that have been shared with you anywhere within Google Drive. You can do this by right-clicking on the file and selecting “Remove”. Remove them from the share from Google Drive’s web client.

So your options for clearing files in the “odrive trash” that are not allowed to be deleted in the cloud is to: Since you can’t delete it, it is put back where it belongs. This is done so that the file is not stuck, invisible, in the odrive trash. When that happens odrive “restores” the file by adding the placeholder back to where it was originally deleted locally. Google responds back and says that your user does not have permission to delete that file. When you choose to empty the trash, odrive tries to tell Google Drive to delete that file. In the case of Google Drive’s “Shared with me” folder: If you end up deleting an item locally in the “Shared With Me” folder, it is, again, sent to the “odrive trash”. If you choose to “restore” the file, it adds back the placeholder file (.cloud) locally, where it was deleted. When you empty the trash, odrive send the command to the cloud storage to delete that file. When that happens, odrive picks up that the file is now gone and stores the potential delete command for the cloud in the “odrive trash”. Entries end up in that queue when files that exist in your cloud storage are deleted on your local system. All it is doing is holding the delete command from going to the cloud, until you say to send it. The odrive trash isn’t storing anything physical.