Bug 254354

Summary: net/rsync --crtimes, -N: preserve creation/birth time is not supported
Product: Ports & Packages Reporter: Fab <Fabiane49b.r>
Component: Individual Port(s)Assignee: Rodrigo Osorio <rodrigo>
Status: New ---    
Severity: Affects Only Me CC: akw24542, emaste, lwhsu, pof10534
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Bug Depends on: 254823    
Bug Blocks:    

Description Fab 2021-03-16 21:15:12 UTC
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.
Comment 1 Li-Wen Hsu freebsd_committer 2021-03-17 04:28:08 UTC
(In reply to Fab from comment #0)
Over to net/rsync maintainer. Although personally I think this should (or at least should also) to report to the upstream.
Comment 2 Peterr346 2021-03-27 01:14:15 UTC
(In reply to Li-Wen Hsu from comment #1)
I see that a user in rsync github has created its a report but the rsync developer is not responding back.

I can also reproduce this problem on my FreeBSD 13.0 here and the error message is:
rsync: This rsync does not support --crtimes (-N)
rsync error: syntax or usage error (code 1) at main.c(1767) [client=3.2.3]
Comment 3 akww244 2021-04-06 17:31:50 UTC
rsync developer said:


"BSD doesn't have support for setting the birth value to an arbitrary value on an existing file, so it's not supported in rsync."

Here the report for FreeBSD.