FreeFileSync Forum

I know that FFS doesn't use hashes - that's why FFS can't detect changes before first sync without sync.ffs_db. But maybe implement hashes only for one feature - "first scan" and use only RAM to store hashes at first sync, after that just create sync.ffs_db in usual way...

I found FFS source code ...

I read this:

Using hashes would require software to run locally at each of the locations involved in the sync, which is often not possible.
FFS only needs to run on any single machine that can access each of the locations involved in the sync.


If FFS already can use bit-by-bit comparison with ...

Because files in different locations with identical size and timestamps are not always identical?
Increases data loss risk basically


I agree about the possible loss in other modes... But is there a risk of data loss in comparison mode "File content" + size + timestamp ? I guess no =)
Please add ...