Linux servers one running TrueNAS-13.0-U6 and the other running
TrueNAS-13.0-U3.1.
I connect to both on a Mac via smb over fiber.
Using cp -a also updates the timestamp of the copied file to today and does not
back-date it to the source file.
I’m not really a sysadmin, I’m a time-based media c
That isn't how rsync should work with -a. Is something preventing it
from backdating the file? What is the filesystem? Can you try copying
your 2015 file with cp -a?
On 10/9/24 14:56, McDowell, Blake wrote:
Hi Kevin,
The -a flag in this instance is not back-dating the timestamp of the
cop
Hi Kevin,
The -a flag in this instance is not back-dating the timestamp of the copied
file to the source file. It is modifying it to the time of transfer and leaving
it that way. Then any time I rerun that command it always updates the timestamp
since it is always making it the time of transfer
You are using rsync -a which copies (preserves) the timestamp. Meaning
that rsync will copy the file then back-date it to the timestamp of the
source file. Most copying tools do not do this though cp's -a does it
too. Note that your itemized output says that the timestamp is
different meanin
Hello,
I have a question about how/why rsync updates modification times, which I
haven’t been able to find an answer to.
I have two locally connected storage devices running TrueNAS Core: one is new
and empty, while the other is filled with files.
When I run the following rsync command:
rsync
