I just updated from ver 3.6 all the way to 3.11. On my first compare using
file size and date method it reported all the files as needing copying.
Looking more carefully I see that 3.11 version sees a 1 hour time difference
between my Vista laptop and my QNAP NAS box running embedded Ubuntu LInux and
says they are different.
Looking into the program options and reading the change log for V3.10 I see
that the Ignore 1hour time difference setup option is gone and that FFS now
"automatically" solves that problem.
Well for me it does not automatically solve the issue. Since I would like to
help make FFS better, what more info can I provide to help track down this
error in the automatic method?
gby
V3.11 Auto DST Correction Not Working for Me
- Posts: 7
- Joined: 14 Feb 2010
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
In summary the new DST handling works as follows (hopefully explaining the
observed behavior):
When traversing FAT/FAT32 files with FFS the first time, additional metadata
is saved for each file that allows to reconstruct the time as seen on this
very first retrieval at any later time, irrespective of DST changes. This
metadata is directly encoded into a file's creation time. Obviously this
requires a migration step: Files that older FFS releases saw as equal, but had
in fact a 1 hour difference, now are shown as different, as the metadata
required to reconstruct "correct" times is not available. The new DST handling
however should ensure that times as they are seen now become stable. So a
complete synchronization is necessary once.
viewtopic.php?t=1990
If you find some issues concerning this new handling (it is unique compared to
all other synchronization software available), please add them here.
observed behavior):
When traversing FAT/FAT32 files with FFS the first time, additional metadata
is saved for each file that allows to reconstruct the time as seen on this
very first retrieval at any later time, irrespective of DST changes. This
metadata is directly encoded into a file's creation time. Obviously this
requires a migration step: Files that older FFS releases saw as equal, but had
in fact a 1 hour difference, now are shown as different, as the metadata
required to reconstruct "correct" times is not available. The new DST handling
however should ensure that times as they are seen now become stable. So a
complete synchronization is necessary once.
viewtopic.php?t=1990
If you find some issues concerning this new handling (it is unique compared to
all other synchronization software available), please add them here.