always copy the whole file?

[jw schultz]

On Sun, Aug 03, 2003 at 08:20:24PM -0700, jw schultz wrote:
> On Mon, Aug 04, 2003 at 10:55:55AM +0800, AndyWu wrote:
> > Here's how it works in my 2 computers.
> > 
> > First, on auk2
> > # rsync -a auk1::pub/linux.iso .
> > It takes about 4 minutes. Everything is fine.
> > 
> > However, after doing this on auk1,
> > # echo "hello" >> /pub/linux.iso
> > 
> > Then, on auk2
> > # rsync -a auk1::pub/linux.iso .
> > 
> > The execution time of the first command is still 4 minutes.
> > I think it's supposed to be much shorter than the first case?
> > The same results appear in local rsync, too.
> > Is there anything wrong with my commands?
> 
> Unlikely.
> 
> I'll bet that file is several hundred megabytes.  Rsync has
> been known that have some difficulty with checksum
> collisions on files that large.  If you run with -vv i'll
> bet it will report "redoing linux.iso(0)" or something very
> similar.
> 
> With released versions of rsync this is avoidable to some
> degree with the --block-size option.  At one time someone
> produced a list of suitable block/file sizes.  Search the
> archives if this matters to you.  This problem has already
> been addressed in CVS.

To clarify, the fix in CVS is ineffictive unless both ends
are at the same protocol level.  A publicly accessable
rsyncd server aught not to be running an unreleased version
without a user advisory.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt