Why Insync takes so long to actually start sync'ing?

Hello @Joshua_Watson, we do use modified time and not using the whole content, but we’re aware that it can still be slow for some users. We’re still working on making the startup faster for all.

For now, you can use the --skip-local-scan command-line argument to avoid the check on startup.

1 Like

So helpful - thanks. I re-synced the database (it was corrupted), I’m presently comparing it via rsync with the old database to make sure I wasn’t missing anything, then I’ll turn off the local scan for now. I’ll report on how that works when finished.

Will I still sync new files from Drive? Will new files created locally still be synced to Drive? I’m assuming the answer is yes.

@Joshua_Watson Yes, it will.

Thanks, this really saves hours of disk thrashing at boot (Ubuntu 16.04.2 LTS). “Signing in” takes some time too btw, about 20/30 minutes (with disk thrashing).


Fabio