-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net/rsync --crtimes, -N: preserve creation/birth time is not supported #166
Comments
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. |
@WayneD I get the same on Debian and Fedora, rsync 3.2.3 |
@WayneD Please reopen this, I also experience this issue with rsync 3.2.3 on Debian and Fedora. It looks like someone made a patch for this a while ago https://github.com/Homebrew/formula-patches/blob/master/rsync/patch-crtimes.diff in case anybody is looking for it (Source: https://forums.gentoo.org/viewtopic-t-1132995.html?sid=76442243e17d281bfb58008fbb8746db). |
This issue is about crtimes on FreeBSD, which doesn't have full crtimes support (it only sets crtime at file creation and when the mtime moves prior to the creation time). The patch you cited is for OS X, which rsync already supports just fine without any patches. Linux doesn't support crtimes in general, but if someone has a portable extension patch feel free to submit it. |
Has anyone solved this problem? Keep creation time in linux https://unix.stackexchange.com/questions/50177/birth-is-empty-on-ext4 |
@WayneD
Based on this report in FreeBSD Bugzilla.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254354
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.
The text was updated successfully, but these errors were encountered: