It seems to me that insync takes way to long to scan for changes when I run it in linux. Data on our Google Drive Account is ~60GB.
Might this issue be resolved by using 2 different folders/drives for win and linux, or is it just the amount of data which takes insync to scan for ~1hour and then show syncing when the folder is actually up-to-date (according to the win google drive client)?
…or could it be an idea to use insync for win as well instead of the google drive client?
Thanks for any clues to solve this issue,
Best regards,
@Phil_hr: Using the same physical folder with both the clients is not supported and is known to cause conflicts & leads to duplicates. You can’t use the same physical folder with more than 1 Insync instance either as of now.
So you will have to use two separate folders - one for your Insync instance on linux and the other for your Google Drive/Insync instance on Windows.
Is this now possible if Insync is used on both Windows and Linux using the same shared folder with Insync File Matching. (Unlike the Original Poster here, who wanted to use Google Drive on Windows and Insync on Ubuntu).
File Matching - File Matching is here! (New Insync version: 1.3.0) “Insync will now try to match your local (in your filesystem) and remote (in Google Drive) files to avoid duplicates and unnecessary uploads and downloads.”