Actually, reading more into this, it might not be that easy, there’s an open issue on it here that suggests that even though it’s documented in the man-pages it might not actually work in Linux:
opened 01:50PM - 17 Mar 21 UTC
closed 04:20AM - 04 Apr 21 UTC
@WayneD
Based on this report in FreeBSD Bugzilla.
https://bugs.freebsd.or… g/bugzilla/show_bug.cgi?id=254354
> Here you can see that FreeBSD generally supports crtime/btime see the stat command.
>
>
> stat -f "Access (atime): %Sa%nModify (mtime): %Sm%nChange (ctime): %Sc%nBirth (crtime/btime): %SB" /video.mkv
>
> Access (atime): Nov 22 16:07:46 2018
> Modify (mtime): Nov 22 16:07:46 2018
> Change (ctime): Nov 22 16:07:46 2018
> Birth (crtime/btime): Nov 01 01:19:02 2016
>
>
>
> If the user uses rsync (3.2.3) to preserve the crtimes with --crtimes or -N for directories and files, it does not work. It says in the terminal that it is not supported.
I can also reproduce this problem on other BSD systems, such as OpenBSD (6.8) and NetBSD (9.1).
It is generally known that all BSD family and other Unix systems have supported Birth time (`btime`) for files + directories for ages.
This means that a patch in rsync should add that it generally fixes this problem. So that all BSD systems and other Unix systems can use it immediately.
Edit: Maybe modify date is enough?
