Re: [BackupPC-users] rsync fatal error: md4 doesn't match on retry; file removed

[Craig B. <cba...@us...>]

Dale writes:

> some more info :
>=20
> if I run the backup for just one share, then it works fine
>=20
> $Conf{RsyncShareName} =3D [
>   '/'
> ];
>=20
> as soon as I add a second share, the errors start
>=20
> $Conf{RsyncShareName} =3D [
>   '/',
>   '/boot'
> ];
>=20
>=20
> I tried with and without checksum-seed with the same results.
>=20
> It seems as though this only happens with hosts that I have changed the=
=20
> share name around.

I found and fixed this bug, which was specific to 3.0.0beta1 and 3.0.0bet=
a0.
The fix will be in BackupPC 3.0.0beta2. =20

Thanks for reporting it.  Garith Dugmore noticed the same problem
and he was able to run some tests that helped me narrow it down.

Craig

> >From: Craig Barratt <cba...@us...>
> >To: "Dale Renton" <dal...@ho...>
> >CC: bac...@li...
> >Subject: Re: [BackupPC-users] rsync fatal error: md4 doesn't match on=20
> >retry;file removed
> >Date: Sat, 11 Nov 2006 00:09:41 -0800
> >
> >Dale writes:
> >
> > > It does not look like any of the files are changing during the back=
up.
> > >
> > > Also, I think this only started happening since we upgraded BackupP=
C=20
> >from 2
> > > to 3.  It is happening on all our backup servers as well, not just o=
ne.
> > >
> > > Anything I can do to help you debug this, let me know.
> >
> >Ok.  Could you please do a backup with a small list of files that incl=
udes
> >one that fails (or ideally a backup that includes just the single file=
 that
> >fails), and increase $Conf{XferLogLevel} to, say, 8?  Please send me t=
he
> >XferLOG file off-list.  It might be quite large.
> >
> >Are you using rsync checksum caching (ie: --checksum-seed=3D32761 incl=
uded
> >in $Conf{RsyncArgs})?  If so, you could try removing that option.
> >
> >Craig