Displaying 4 results from an estimated 4 matches for "bwag_r2_00135909".
2016 Jun 09
4
rsync keeps writing files over
...-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)...
2016 Jun 11
0
rsync keeps writing files over
...e-changes.
>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
At a certain level this makes sense. Without --times, the timestamps are
not used to determine whether or not a file needs to be transferred and,
in addition, the receiver will set the timestamp to the current time on
the receiver.
This is what the docs mean when they say
"Note that if...
2016 Jun 09
0
rsync keeps writing files over
...>
> 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 complete...
2016 Jun 02
9
rsync keeps writing files over
Cool Thanks!
Specifically, the timestamps on both <src> and <dest> match for "ls -l"
but do not match for "ls -lu" or "ls -lc”
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.
Yes,