Grive removing files that weren't touched at all

[EgbertW]

I'm synching a folder using Grive, called domainWebsites

At first, grive didn't synchronize anything. After I opened the Google Drive web interface and opened the folder 'domainWebsites' grive did synchronize on the next run. I didn't touch anything, i merely opened the folder in the webinterface.

After a couple of days of synchronizing, last light I got the following output from Grive:

Reading local directories
Reading remote server file list
Synchronizing files
sync "./domainWebsites" deleted in remote. deleting local
Finished!

It had not been deleted in remote, or even touched. Once again, after I opened this folder in the web interface and ran grive after that, it would download the folder.

What does opening the folder in the web interface do and why does it cause the files to starting synching again?

[karteek-paruchuri]

Hi MadEgg,

I would suggest you to do this way
grive --dry-run && grive sync .

The dry run would create a meta data file to help the service identify how the file state has been modified. A sync command following that would ensure the state is properly replicated in local as well as cloud storage. I'm following this way and things work fine for me. Let me know how this approach works for you.Good luck

[EgbertW]

Thanks, I'll give it a try, and let you know if the issue occurs again or not!