FreeFileSync Forum

Personally, I feel the default behavior should be FileTimeTolerance = 0 with no round down.

Although FAT is widely used, I wonder how many people actually use FFS for USB drives formatted in FAT rather than simple copy-paste. I personally only use FFS on my PC or external SSD and turn on version ...

I figured out the issue:

When batch editing files (like using VSCode's Ctrl+Shift+F), each file will have only a few milliseconds difference in timestamps.

If I overwrite files with such tiny timestamp differences, and the file size hasn't changed (for example, changing "Attribute = 0" to ...

I'll need to look into this more, but honestly I'm scratching my head about why FreeFileSync needs to round down at all. Isn't that what FileTimeTolerance is for?

It would be nice to have an option to disable round down. I use FFS to sync millions of files, and some files have problems with this.

I haven't tested more files, but I guess files with time differences under 100ms or 1000ms would be considered equal.

Hi
I noticed that even when I set FileTimeTolerance to 0, FreeFileSync still treats files with timestamp differences between 2ms to 77ms as identical.

After setting FileTimeTolerance to 0, I did notice more files being detected as different compared to the default setting. But such small timestamp ...