FFS changes file timestamp (modified date-time) when synchronizing

Get help for specific problems
Posts: 4
Joined: 5 Jun 2019

vadkot

1) FFS changes file timestamp (modified date-time) when synchronizing.
2) Two way synchronizing algorithm isn't correct: trying to overwrite newer file.
On the following picture - default FFS settings. The same file. After synchronizing, file has new timestamp.
Attachments
ffs_trouble_1.png
ffs_trouble_1.png (62.02 KiB) Viewed 1585 times
User avatar
Site Admin
Posts: 7052
Joined: 9 Dec 2007

Zenju

This is probably explained by some process changing the file on the network share after sync:
https://freefilesync.org/faq.php#different-after-sync
Posts: 4
Joined: 5 Jun 2019

vadkot

I have SMB share under *nix OS on FAT32 flash.
When I copy file from Windows to SMB, modified date changes everytime to current.
It's normal, because SMB OS file system decides which date to set.
BUT!
When I copy file from SMB to Windows, it's Windows OS decides which date to set.
When I copy with Win Explorer, modified date changes to current system time.
When I copy with Robocopy from CMD, modified date stays the same as on SMB file.
So FFS works as Win Explorer and changes modified date to current system.
You should correct FFS code to work as Robocopy works, when copy from SMB shares.
This is FFS problem and not OS.
Attachments
ssf_issue_2.png
ssf_issue_2.png (222.24 KiB) Viewed 1546 times
ssf_issue_1.png
ssf_issue_1.png (70.87 KiB) Viewed 1546 times
User avatar
Site Admin
Posts: 7052
Joined: 9 Dec 2007

Zenju

Windows Explorer also transfers the modification time, just like RoboCopy. So I suspect that there is some other process changing the file time directly after copy. This can be checked using Process Monitor as explained in the link above.
Posts: 4
Joined: 5 Jun 2019

vadkot

You are wrong. I showed you the real situation on screens.
Why You deny the obvious?
Win Explorer and Robocopy work differently with the file date when copy from SMB share.
Moreover, Sysinternal Process Explorer clearly shows:
That only 1 process holds the file: either Win Explorer or Robokopi.
No any mystical processes that changes file after copy from SMB!
User avatar
Site Admin
Posts: 7052
Joined: 9 Dec 2007

Zenju

You have to read more carefully. I didn't write that Windows Explorer was actually successful in copying the modification times. It obviously failed, this already proofs that it's an issue unrelated to FreeFileSync. But anyway you can still use Process Monitor to find out what's going wrong on your system.
Posts: 4
Joined: 5 Jun 2019

vadkot

You write some kind of nonsense
At first you claim that win explorer work, as well as robocopy.
Then say no.
I specifically showed you that robocopy does NOT change the modification date.
In my system - everything is OK.
The problem is in code of FFS.
I have already written a power shell script that makes synchronization through robocopy and do it without the FFS.
I hope You will explore and correct troubleshooting, that I have given to you, having spent my time and money.
User avatar
Site Admin
Posts: 7052
Joined: 9 Dec 2007

Zenju

Good luck finding a solution to your problem somewhere else. With your kind of social skills you'll need it.