FreeFileSync Forum

I knew about that, but this is not a physical drive in the server, but on another machine. The solution described does not work in this case. The version I tested the last time worked fine!

No problem! The 'final' works great!

Copy with the preserve timestamp works. Here is the strace:
https://dl.dropboxusercontent.com/u/10558681/cp_log.txt

Version 2 seems to work. I only has the following message twice during the whole operation (in the terminal):

ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred

Sure:

https://dl.dropboxusercontent.com/u/10558681/ffs_log.txt
https://dl.dropboxusercontent.com/u/10558681/touch_log.txt
https://dl.dropboxusercontent.com/u/10558681/touch1_log.txt

In the last one I use command 'touch -d "two hours ago" <filename>

Could it be that the call is incorrect?

Alas...

Cannot write modification time of "/media/m8/hdd/tv/2 Broke Girls/Season 01/2 Broke Girls - S01E01 - Pilot.avi.ffs_tmp".

Error Code 22: Invalid argument (utimensat)

I get the following error:

Cannot write modification time of "/media/m8/hdd/tv/2 Broke Girls/Season 01/2 Broke Girls - S01E01 - Pilot.avi.ffs_tmp".

Error Code 22: Invalid argument (utime)

Ok, I have tested the version you posted. I had to install some additional libraries first, but no real issue. Some icons do not have pictures btw.

I get the following error:
Cannot write modification time of "/media/m8/hdd/tv/The Block All Stars/Season 10/The Block - S10E22 - Bedrooms Revealed.mp4 ...

It may be, although it does not seem to work on Ubunty with CIFS/NTFS. Perhaps a fallback option? I like the program on Windows, but this issue makes it unusable to use on my server it seems.

A quick additional note, touch uses utimensat instead of utimes on Ubuntu. So, perhaps if utimensat instead of utimes was used, it would also work.

I am unable to sync between my Ubuntu server and my mediaplayer. I get the errors like the one in the subject header. It seems that it fails when the time of the file must be adjusted (of the .ffs_tmp files to be exact). From what I have gathered, it might be a problem of the implementation of NTFS ...