FreeFileSync Forum

Yes @therube, that seems like an excellent solution.
As I am relatively new to FFS, do you believe there are good chances that this will be implemented fairly soon? What is the procedure for suggesting a new feature? Does the developer frequently monitor this forum?

Thank you very much for your ...

I wonder if it could be implemented in the future as it seems like a pretty easy feature to add.
(I might be wrong by missing a few edge cases…)

Thanks for the details.
I can't proceed with this @therube as those files are shared with clients and colleagues.

So in my situation, FFS would be effective if it had an additional mode that utilizes the database file to verify if the file has already been copied.
If so, it would then be ...

Yes indeed, the metadata has been changed.
So do you mean it's the expected behavior?
I thought that after a file had been copied to the target destination, we could do anything to the copied file (including deleting the file), FFS would never resync the file from the source destination.

Here is a few more info:

I'm using FFS 13.8 on a M1 2020 MacBook Air running Sonoma 14.4.1

Hi FFS,

I'm using FFS exactly for the awesome new UPDATE mode.

However, I have noticed an inconsistent issue.

Very often but not always, after renaming a few files on the target destination, FFS detects the original files on the source destination as new files.

Any idea what could happen?