Problems under Zorin Linux

[rahzan]

Hello.
I have recently switched from windows-10 to Zorin Linux.
Freefilesync is a very important piece of what I do everyday for back up to a NAS.

1. I have ver 14.8 I have downloaded v 14.9 for linux in tar.gz format but how do I install it?

2. I did a manual copy of all files (in the Documents folder) to a new folder on the NAS, but when I run the COMPARE function, it seems it wants to overwrite ALL the files which have the same size and date. Is something wrong? will it try to do this every time?

3. I allowed it to start to Synchronize (Mirror mode) for each file copied there is the warning or error:" cannot set the modified date, function not supported" (paraphrased).

I would very much appreciate any help to get this working without doubt about what is actually uploaded.

[xCSxXenon]

2 and 3 are related. How did you transfer the data from your Windows environment to Linux? Something between the Linux OS and the NAS is causing timestamps to be out of whack, so FFS thinks that all files are different. Make sure the NAS is fully up to date.

As for 1, pretty common thing to do in Linux. Why are you moving off Windows?

[rahzan]

Thanks for your reply.
I extracted the tar.gz and there was .run file which I ran and seemed to work.
I had only done flatpacks and apt installs until now; I asked because I did not want to do anything that may break things; .run will be fine as well.

For the initial copying, I used the FILES application and dragged and dropped the full Documents folder from the NAS folder to the pc's hard drive. I thought that was faster than the one by one copying through FFS.

Do you suppose if I let FFS overwrite the NAS folder, it will fix the problem going forward?

[xCSxXenon]

Do you suppose if I let FFS overwrite the NAS folder, it will fix the problem going forward?

Hard to say. If you run a compare, FFS will tell you why the files on each side are different. It should also tell you what that different value is for each file on each side. I'm guessing modification time is the value that is being detected as different. For one side or the other, local or on the NAS, do all of the files show the same timestamp?

My best guess is that the NAS is connected in a way that isn't exposing the timestamp correctly or vice versa.

[rahzan]

I decided to clear out the NAS copy (that was made with simple drag-drop copy within the file manager) and let FFS copy everything (by mirroring synch) from scratch to see how it goes.

But there was one file (name=Instlmslw-1482.ffs_tmp) which would not be deleted because it is still "open".

It remain "open" even after a reboot. Are you able to say what process is holding this open even after a reboot? My various attempts to find our the Process ID as well as trying to run the UNINSTALL.SH have failed. Various security protocols under Linux don't allow it.

I'd appreciate it if you can help decipher what process name or identifier this is under so I can terminate it.

[rahzan]

I shut down the pc and deleted the file on the NAS from another pc. I will describe the problem that keeps occurring with ".ffs_tmp" files once I can decipher the warning messages.