Creation date not synced?

[swswsws]

Hi, after syncing I found that files in the destination folder all showed as created on 1 January 1970 01:00. Is this a bug or was I missing something in the settings? I'm on Mac and I was moving from a Mac OS Extended (Journaled) drive to a NTFS drive (via Paragon NTFS driver), but later I used ntfs 3g instead since I upgraded to macOS 15. The problem persisted. Thanks for any advice.

[xCSxXenon]

FFS keeps timestamps by default, there shouldn't be anything you explicitly have to set up.
Maybe related? https://forum.scootersoftware.com/forum/beyond-compare-4-discussion/mac/91353-file-copy-on-mac-to-retain-timestamp/page2
Different software, similar issue. Granted, that was with exFAT/SMB and nothing mentioned NTFS. I wonder if it's even possible since NTFS isn't a natively support filesystem on Mac OS. The ability to preserve timestamps may be the burden of the FUSE implementation, Paragon NTFS Driver and NTFS 3G in your case

[therube]

What are the source file dates?

1-1-1970 is a "special" date (epoch date on Unix systems).

So maybe if source file dates are before that?
Or, some sort of bug somewhere along the line, that is causing an invalid date, so being set to '0', hence 1-1-1970?

[swswsws]

Thanks for the answers. I can confirm that this is not a problem with FFS. I plugged the drive in my Windows PC and the creation dates appeared fine. Maybe a display bug with FUSE or NTFS-3G.

https://github.com/osxfuse/osxfuse/issues/501