Hi Steven,

Yes, both file systems are the same.

rsync -nri --modify-window=1 <src> <dest>

Gives me the following for most files >f..T.......
2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/
BWAG_R2_00138428.dpx
Although a few have  >f..T......n
2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/
BWAG_R2_00135909.dpx

Strangely, no matter what HDD I¹m transferring from it is always the same
sequence of files that have the n - "A n means the create time (newness)
is different and is being updated to the sender's value (requires
--crtimes).
(I¹m not quite sure I completely understand ‹-modify-window)

Here is a <dest> file example of timestamps as rsync interprets them:
-rwxrwxrwx     24,839,552 2016/06/08 13:13:19 BWAG_R2_00086400.dpx

Here is a <src> file example of timestamps as rsync interprets them:
-rwxrwxrwx     24,839,552 2016/05/27 13:43:32 BWAG_R2_00086400.dpx



So, yeah, that is the problem, apparently. The timestamps are
transferring. 

But, for the files that have the ³n² the timestamps appear to be fine and
those ones don¹t continually transfer. A mystery to me as to why the
timestamps work on these particular files.

<src>
-rwxrwxrwx     24,839,552 2016/05/27 14:00:57 BWAG_R2_00130798.dpx
<dest>


-rwxrwxrwx     24,839,552 2016/05/27 14:00:57 BWAG_R2_00130798.dpx

I¹m running version 3.1.2 protocol 31.


Thanks,
Blake


On 6/2/16, 7:26 PM, "rsync on behalf of Steven Levine"
<rsync-boun...@lists.samba.org on behalf of stev...@earthlink.net> wrote:

>In <d3762d63.17a7%mcdowe...@si.edu>, on 06/02/16
>   at 10:42 PM, "McDowell, Blake" <mcdowe...@si.edu> said:
>
>Hi Blake,
>
>>The storage is just an regular HDD in a mac pro tower. I can t imagine
>>why it wouldn t handle timestamps. Also of note - this problem doesn t
>>exist for every file, just the vast majority. So, that just makes it more
>>confusing. 
>
>Are the file systems the same on the source and the destination
>partitions?
>
>Check out
>
>  --modify-window
>
>in the help.  If the source and destination file systems have different
>timestamp precision, this is the usual solution.
>
>You can also try
>
>  rsync /path-to-foo
>
>where path-to-foo is a directory or file.  This will list the file
>timestamps as rsync interprets them.
>
>BTW, what version of rsync are you running?  It might matter.
>
>Steven
>
>-- 
>----------------------------------------------------------------------
>"Steven Levine" <stev...@earthlink.net>  Warp/DIY/BlueLion etc.
>www.scoug.com www.arcanoae.com www.warpcave.com
>----------------------------------------------------------------------
>
>
>-- 
>Please use reply-all for most replies to avoid omitting the mailing list.
>To unsubscribe or change options:
>https://lists.samba.org/mailman/listinfo/rsync
>Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Reply via email to