The first time it happened, it was very painful and nearly cost me data, since I had a nightly batch script running two-way synchronization. I have experienced issues with Google Drive a few times like those described by t0ma5, though I was using a Google Shared Drive as a backup for local files, rather syncing two Drives. ![]() I am using Windows 10 and FFS v11.3 (same problem with v11.2)ĮDIT: A quick fix is to delete the DB file inĬ:\Users\YOU_NAME\AppData\Roaming\FreeFileSync\GoogleDriveĪnd run all the scans again to rebuild a new DB that works for some time until it gets corrupted again. ![]() The folders in question (source and destination) have about 1.5TB of data. So it read both (source and destination) wrongly and suggests actions that are not necessary to perform. I open the team drives on my browser and I can see all the files that FFS can't see, I can open them and download them without a problem, but FFS says the items are not there.Īlso it reads the destination folder with mistakes claiming some files/folders don't exist and it need to copy them (but again, I can see/use those files with my internet browser). ![]() I use FFS to sync/mirror two Google Team Drives (AKA Shared Drives) and it used to work perfectly, but not anymore, this is my problem:įFS was working just fine until two days ago when out of the blue, without changing any configuration or setting, FFS stopped reading files correctly in both folders (source and destination) so it tries copy and delete files without any need for it.įFS claims that many files don't exist on both sides by displaying this message:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |