date after sync are "sync date" and not "file create date" : sync went wrong

Posts: 4 · golfy038 17 Jun 2022, 09:18

Hi there,

sorry about my title which is not clear, but here is the explanation:
1) I've choose "Synchronization" for my first synchronization between a NAS folder (/mnt/myName/Projects) and my local folder (/home/myName/Projects)
2) FreeFileSync have create missing files from two sides (local and remote)
3) I'm asking to compare and now FreeFileSync propose me to sync ALL files from remote to my local

When I display date, remote date are the time of first synchronization

I'm on Linux Manjaro and I use FreeFileSync 11.21 with a Synology NAS. This folders (and files) were created with Win10, before my migration to Manjaro (ext4 for local, CIFS for remote)
If anyone has an advice or a tips to help me doing better sync... thanks !

Posts: 4866 · xCSxXenon 19 Jun 2022, 14:11

This is most definitely a NAS or Linux issue. What happens if you copy the files manually from NAS to local?

Posts: 4 · golfy038 19 Jun 2022, 14:31

It works like a charm
https://i.imgur.com/0jamkk6

Posts: 7505 · Zenju 19 Jun 2022, 19:17

Can you make a screenshot of the error log when copying with FFS?

Posts: 4 · golfy038 20 Jun 2022, 08:48

yep of course!

No change have been done since last synchronization on 2016 folders and you can imagine I'm not modifying so much files in few days.
Even when running many time FreeFileSync, it has always lot of files to sync (often conflit with date).

I'm trying to change smb to nfs but I've some problem with permissions for now...

Posts: 7505 · Zenju 20 Jun 2022, 09:04

With no errors in the log, this means that setting modification times (using utimensat()) fails silently outside the control of FFS. This leaves only two explanations:
1. a bug in the NAS firmware
2. a bug in the software mounting the NAS (e.g. gvfs)

This is most definitely a NAS or Linux issue. What happens if you copy the files manually from NAS to local? xCSxXenon, 19 Jun 2022, 14:11

The other way round is the interesting case.

Posts: 4 · golfy038 22 Jun 2022, 15:00

Maybe it's NAS problem, maybe not.
If I used Unison, it works well : Unison isn't able to monitor files in real-time, but it does the job correctly.
Results with FFS aren't reliable for now :(
I'll give a try to lsyncd too if I've time...

Posts: 1 · dri 24 Oct 2024, 11:43

I have the same problem. You create a file locally, sync it to the NAS and the next time you sync, the file should be synced back to the client.
The NAS knows a change date and a creation date for a file. When syncing under Windows, FreeFileSync reliably transfers both values to the transferred file. Not under Linux. When syncing, the time of copying is set as the change and creation date in the file on the NAS. This means that the synced file on the NAS is newer the next time it runs and should be copied back.