Hi all,
If you are experiencing syncing metadata issue on occasions other than just after the starting or resuming Insync, kindly send to us the compressed copy of the dbs folder (present next to the logs.db file) along with the logs. Create the copy of the dbs folder while Insync is running and stuck.
Our findings so far have been as follows:
-
It happens upon the start if there are large number of files being sync’d locally - Insync gets busy scanning the local folder for changes on priority and transfers are deferred. This issue gets aggravated if the Insync folder is on a network drive or if Insync is paused & resumed or if Insync folder goes missing & is reinstated. We are working on improving this behaviour.
-
Sometimes, making changes to certain drive files/folders (and for some users, even browsing a file/folder online on Google Drive web) triggers a lot of metadata changes in the Google Drive feed. This makes Insync go to “Syncing metadata…” state. We haven’t been able to replicate it for any of our accounts but we have observed this on users’ machine during remote desktop support session and confirmed it through their Insync databases. This could be an issue at Google’s end as well. Our finding so far is that this is folder/file specific issue (i.e. it happens when changing/browsing certain files/folders in an account) but we haven’t been able to make any further progress on it.
-
In two reports, it has been reported that Insync is stuck and 1) & 2) do not apply. We are seeking further info from the users to see what exactly happened in their case.
Thanks
If anything we could assist you with, just send us an email to 