rsync keeps writing files over
Kevin Korb
kmk at sanitarium.net
Thu Jun 9 00:24:23 UTC 2016
the T means that the timestamp is wrong and rsync is not fixing it
because you don't have --times or --archive in your command line.
On 06/08/2016 08:17 PM, McDowell, Blake wrote:
> 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-bounces at lists.samba.org on behalf of steve53 at earthlink.net> wrote:
>
>> In <D3762D63.17A7%mcdowellh at si.edu>, on 06/02/16
>> at 10:42 PM, "McDowell, Blake" <McDowellH at 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" <steve53 at 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
>
>
--
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
Kevin Korb Phone: (407) 252-6853
Systems Administrator Internet:
FutureQuest, Inc. Kevin at FutureQuest.net (work)
Orlando, Florida kmk at sanitarium.net (personal)
Web page: http://www.sanitarium.net/
PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/rsync/attachments/20160608/2ea21f07/signature.sig>
More information about the rsync
mailing list