The time offset does not take effect immediately!

Posts: 10 · rainman74 5 Jul 2022, 22:14

The time offset does not take effect immediately, but you have to enter the time again after each comparison.

Even if you save it in a ffs config file, it will be saved correctly but not used immediately when loading and comparing.

Saved correctly - but doesn't work when loading and running the comparison!
<IgnoreTimeShift>1</IgnoreTimeShift>

Posts: 7506 · Zenju 6 Jul 2022, 08:35

The time offset does not take effect immediately, but you have to enter the time again after each comparison. rainman74, 05 Jul 2022, 22:14

Entering the time shift *clears* the comparison results. So there doesn't seem to be any way for it to have no effect.

Posts: 10 · rainman74 6 Jul 2022, 12:15

The time offset does not take effect immediately, but you have to enter the time again after each comparison. rainman74, 05 Jul 2022, 22:14
Entering the time shift *clears* the comparison results. So there doesn't seem to be any way for it to have no effect. Zenju, 06 Jul 2022, 08:35

This is not correct. Entering a time shift indeed filters the result according to the corresponding time differences. This works, but you can save this setting in the ffs config files, but it will not be respected after calling a config file. Only if you then type it in manually each time after a comparison.

(I sync from Windows -> SMB shares)

Posts: 7506 · Zenju 6 Jul 2022, 12:30

Apparently you're messing with the ffs_gui file directly, instead of using the sync config dialog (F6).

Posts: 10 · rainman74 6 Jul 2022, 12:33

Apparently you're messing with the ffs_gui file directly, instead of using the sync config dialog (F6). Zenju, 06 Jul 2022, 12:30

No, I configure exclusively via the GUI. I had only shown the excerpt from the file so that you can see that it is set correctly.

Posts: 7506 · Zenju 6 Jul 2022, 13:26

It's unclear what exactly you are doing. Maybe a video, or step by step instructions would help.

Posts: 10 · rainman74 6 Jul 2022, 14:16

It's unclear what exactly you are doing. Maybe a video, or step by step instructions would help. Zenju, 06 Jul 2022, 13:26

1. I load the config file "TEST" (in this config file a time offset of 2 hours is set as an example)

2. I click on COMPARE

3. Two file results are displayed as "different", although the files have less than two hour different creation date! This is wrong!

Posts: 7506 · Zenju 6 Jul 2022, 14:17

This is not how ignore time shift works. See: https://freefilesync.org/manual.php?topic=daylight-saving-time

Posts: 10 · rainman74 6 Jul 2022, 14:24

This is not how ignore time shift works. See: https://freefilesync.org/manual.php?topic=daylight-saving-time Zenju, 06 Jul 2022, 14:17

Ok, but then FreeFileSync is unfortunately useless for me, because when syncing via SMB to my NAS such differences occur and I can not exclude them in the program.

For me "my" logic of how the timeshift works would make more sense ;-)

Posts: 7506 · Zenju 6 Jul 2022, 14:30

when syncing via SMB to my NAS such differences occur and I can not exclude them in the program. rainman74, 06 Jul 2022, 14:24

This doesn't sound right. File modification times should only change when the file is actually modified (with the exception of Daylight Savings time, which is a legacy issue). Otherwise this indicates that some other software is messing with the files, but shouldn't.

Posts: 10 · rainman74 6 Jul 2022, 14:37

when syncing via SMB to my NAS such differences occur and I can not exclude them in the program. rainman74, 06 Jul 2022, 14:24
This doesn't sound right. File modification times should only change when the file is actually modified (with the exception of Daylight Savings time, which is a legacy issue). Otherwise this indicates that some other software is messing with the files, but shouldn't. Zenju, 06 Jul 2022, 14:30

I use a Synology NAS with the current DSM 7.1. This is nothing unusual and millions of times in use. But yes, apparently here the NAS does something different when copying than you expect. Therefore, my logic would be easier to understand, especially if you want that certain time differences are simply accepted as EQUAL.

Could it be an issue with the Create/Modified and Accessed timestamp? Maybe FreeFileSync is comparing the wrong date here?

Or could this be changed to "my" logic? That would then cover everything, right?

Posts: 1202 · therube 6 Jul 2022, 16:08

Further explain the process?

You have a source file of such & such a date.
And you have a target file of such & such a date.

And FFS wants to update the source to the target.

And you update.

And then what?
What were the files date/time to begin with - on each end.
And what were the files date/time that you ended up with - on each end.

Particular Synology utilities can/will see an "update" to a file - that resulted in no change to its' contents - except for date/time difference, & will revert that change - on the NAS end (so the NAS will show the older date [of an otherwise identical file]).

viewtopic.php?t=7396p24922

Posts: 10 · rainman74 6 Jul 2022, 16:25

Further explain the process?therube, 06 Jul 2022, 16:08

The process looks like this:

I sync my files with FFS from a NTFS hard disk under Windows to the Synology NAS (to a NTFS disk connected via USB).

According to FFS everything looks fine and the sync was successful. When resyncing, no differences are detected for now.

Then after some time, when I do a sync again, suddenly time differences are detected for all files copied by FFS via SMB! But no time differences are detected on the other older files I copied to the disk when it was still connected directly to the PC via USB.

I thought now, I get the differences, which seem to be only because of the timestamps, per FFS with this setting under control. But unfortunately that does not work either :-(

With which date/time did you start the files - on both sides.
And with what date/time did you end the files - on both sides.

I will report that at the next sync....