When I unsync a file or folder using the Selective Sync option in version 1.2.6, the folder/file disappears from the directory but it still takes up memory on the local hard drive. I checked the Trash to make sure it did not need to be emptied. There are no files in the Trash.
What is the best method for removing a folder from a local hard drive to free up space but keeping it on the Google Drive to sync with other computers?
I’m having the same challenge (Mac 10.10.3 with Selective Sync 1.2.6) @roald - is this an issue your engineers are aware of? Thanks in advance for your help!
I am having the same issue. Moved a folder to google drive and then selectively unsync in insync and the file is not visible but the space is still being taken up on the drive.
I’m pretty sure I’m experiencing the same behaviour on OSX 10.10.3. The file is neither in the system trash nor in the .insync-trash folder. Yet, I’m missing the whole space on my system. Any idea why?
Opps, sorry for the delay. I was taking an internet break for a week on vaca.
Not sure I understand the question. I do not know what “disable .insync-trash entirely” or “manually clear it” means.
I would envision this working similar to the way dropbox does it. If you uncheck the folder, then the folder disappears from your computer, you can continue to access the file(s) in the cloud but the file(s) are removed from your computer and thus the space is cleared from your computer. This is what the warning message says happens when you do this:
“You have unselected some files and folders. They will be removed from this machine, but will remain on your Google Drive.”
But what happened with me is that I can no longer see the file(s) on the machine but the space on my computer is not freed up. The file(s) are also not in my trash so it is not a matter of my simply clearing my trash to free up the space.
I am doing something wrong? As I really can’t imagine any other way this feature would work.
@Gregory_Jacobson I see, and I understand. No, you’re not doing anything wrong, it’s just that deleted and unsynced files are currently stored for a time in a local cache folder named .insync-trash before getting actually deleted.
I will discuss some possible solutions with the team, including simply deleting selectively-unsynced files directly, and will update this thread. Thank you for the feedback!
@Luis_Arias There’s no problem with removing the .insync-trash folders manually.
Improving the behavior of selective unsyncing is still being discussed internally. I will post in this thread again once it’s confirmed to be included in an upcoming version.