<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:eharvey@lyricsemiconductors.com">eharvey@lyricsemiconductors.com</a> wrote:
<blockquote cite="mid:000301ca2dab$2e320cd0$8a962670$@com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<div class="Section1">
<p class="MsoNormal">I thought rsync, would calculate checksums of
large files
that have changed timestamps or filesizes, and send only the chunks
which
changed. Is this not correct? My goal is to come up with a
reasonable (fast and efficient) way for me to daily incrementally
backup my
Parallels virtual machine (a directory structure containing mostly
small files,
and one 20G file)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’m on OSX 10.5, using rsync 2.6.9, and the
destination
machine has the same versions. I configured ssh keys, and this is my
result:</p>
</div>
</blockquote>
Upgrade to rsync 3 at least.<br>
<br>
Rsync keeps a hash of the blocks of sliding hashes. For older versions
of rsync, the has was of a constant size. This meant that files over
3GB in size had a high chance of hash collisions. For a 20G file, the
collisions alone might be the cause of your trouble.<br>
<br>
Newer rsyncs detect when the hash gets too big, and increase the has
size accordingly, thus avoiding the collisions.<br>
<br>
In other words - upgrade both sides (but specifically the sender).<br>
<br>
Shachar<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>