- Freefilesync cannot open directory dfound.000 update#
- Freefilesync cannot open directory dfound.000 manual#
- Freefilesync cannot open directory dfound.000 windows 10#
- Freefilesync cannot open directory dfound.000 software#
- Freefilesync cannot open directory dfound.000 download#
Freefilesync cannot open directory dfound.000 manual#
However, since I anticipate there being another issue like this in the future, I have disabled all automatic nightly backups to Google Drive and will monitor for this problem in the future whenever I run a manual backup. This time, the comparison refreshed accurately, and a new sync.ffs_db was created.Īs of this writing, all is working as expected. This had no effect on the comparison, and a new sync.ffs_db was not immediately created in its place.įinally, I disconnected and reconnected my Google Drive account a second time. Now there were not two or one database files, but zero. So, next I tried deleting the old sync.ffs_db in Drive also. When I tried to actual perform the sync (not just a comparison) on the non-existent file, I got this message:
I tried emptying the Shared Drive's trash, but that made no difference. Since I did not want to keep them, I deleted them in the Shared Drive manually, but when I re-ran the comparison, it still claimed these deleted files were in the Shared Drive, ready to be synced. As expected, these files were showing in my two-way comparison as being ready to be copied locally. The following may be an independent problem, or it might be caused by the changing sync.ffs_db file:Īfter getting that to work, the file comparison helped me realize that some files needed to be deleted from the Shared Drive they were mistakenly placed there by a collaborator. This time, there was no error, and the file comparison gave the expected results, albeit somehow ignoring the duplicated files on Drive. I then deleted the newer copy of sync.ffs_db and reran the two-way sync. Indeed, there were now two copies of the file in the Shared Drive. The name sync.ffs_db is used by more than one item in the folder." When I attempted a two-way comparison again, apparently a new sync.ffs_db was created in the Shared Drive.
Freefilesync cannot open directory dfound.000 software#
But today I felt like trying to solve the problem, and I quickly stumbled upon this thread.įollowing Zenju's suggestion (thank you for this software by the way despite this post, I absolutely love it, and am already a regular donor!), I tried disconnecting and reconnecting my Google Drive account. Like the first time, if I had still been using two-way mode for my nightly script, I would have lost files.Ī little frustrated, I just walked away from it for a couple weeks, letting those duplicated files sit there. When I asked it to do a comparison in two-way mode, it showed that it thought many of the Drive files were deleted, and it wanted to remove them from my local machine.
Freefilesync cannot open directory dfound.000 update#
I deleted those duplicates by hand and wondered what was going on.Īpparently I'm a slow learner, because I let it happen a third time in one-way update mode, so duplicate files appeared in Drive again.
Gigabytes of files were just deleted one day! Luckily, I had other backups! I changed the two-way sync mode on my nightly script to a one-way update instead this worked fine initially, but sometime later duplicates of files appeared in Drive, since it apparently thought those files weren't on the Drive any more. 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.
Freefilesync cannot open directory dfound.000 windows 10#
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.
Freefilesync cannot open directory dfound.000 download#
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 kommentar(er)
