FreeFileSync Forum

I find a file named sync.ffs_db in each of the directories.
Suprising point is that one of these files does exist, but has no entries in the properties: "created","last modified" and "last access", while the other have these properties filled.
What does that mean?

The distant directory ist a SMB ...

Just to add my Sychronisation-Settings, I include this screenshot

When I delete a file in one directory (I call it source here), it will be restored in the syncing process from the other directory (I call it target here).
Similar problem:
When I move a file of the source directory to a subdirectory below the source directory and start the syncing process, with the ...

I'm confident, Your are right, the file table is corrupted.
The question is: *How* did this happen.

That are exclusively exactly these .ffs_db files. Never another one. And this problem occurs exclusively on the distant system, never on the local one. It happens rarely, but repeatedly, from time ...

I have a few files with the extension .ffs_db , created on a distant NAS drive, which make problems.
The NAS runs a SMB Server to organize data handling. I'm using FreeFileSync on a Windows Pro 64 bit verions 10.0.19045 Build 19045 PC, running the FreeFileSync version 12.0.
It was the same with the ...

If I use any tools for deletion (Windows file explorer, Total Commander, 7-zip compressor, Windows Command Shell), they all complain, that the files to be deleted does not exist.
But it is displayed in the file explorer and other file managers.

There is a file "filename~53d6.ffs_tmp" on one of both sides of the FFS-comparison. "filename is an existing MS-Excel-file, but there are more files and none of them is the base of other *.ffs_tmp files.

This file exists only on one side of both, on the distant SMB-system.

It has the
•size 0 KB ...

After the syncronisation, I tried another comparison of the two file systems without any error message now.

I used FreeFileSync for a few months now and it worked great.
One part of the syncronisation is the local PC working with Windows 10 Pro ,
the other one a distant fileserver is communicating through the SMB protocol.
This was the setting also before the error messages occured.

Now, suddenly ...