Lots of files seem to be considered 'changed'

For a sample updated file in the UTC-5 time zone
Windows File Explorer says ‎Wednesday, ‎November ‎27, ‎2019, ‏‎6:58:13 PM
Remote dlist file says “time”:“20191127T235813Z”
Lastmodified in DB FilesetEntry says 637104958932588928
https://www.venea.net/web/net_ticks_datetime_converter#net_ticks_to_date_time_and_unix_timestamp_conversion convert:

Unix Timestamp:

  • round down: 1574899093
  • with fractional part: 1574899093.2588928

GMT / UTC Date Time: 2019-11-27 23:58:13 + 0.2588928 second

so what might be happening is that the DB has high resolution normally, but Recreate rounds it down.
There is also other metadata stored separately (such as ACLs on Windows), but I don’t know formats.

This is rather reminiscent of an issue @drwtsn32 ran into here where a mono upgrade to 5.12.0 and later picks up more resolution than it used to, thus triggers scans, but shouldn’t upload any file blocks.

I don’t know why the dlist file saves the file time in second resolution. .NET ticks are 100 ns resolution.