Re: [rdiff-backup-users] librsync: ERROR:

[Robert Weber]

The problem happens on files of all kinds, some have restrictive modes,
some don't.  Some are smaller, some are the same size, some are larger.
Files like /etc/shadow don't copy.  I have mailed the folks at librsync,
but I was able to run rdiff to delta an patch the files without a problem
so it may be how rdiff-backup is running rs_file_copy_cb, possibly with a
negitive pos value(or a pos value that is not of type off_t or long long).
Either way, can we get a switch in rdiff-backup that will just rcp the file
in this case?  My entire mirror(>4Tb) is useless now because of these
errors, and I am looking into doing the scp's by hand as a stop-gap.  This
problem may be elsewhere, but it appears to be a problem with solaris
clients.


--
2 3 5 7 B D 11 13 17 1D 1F 25 29 2B 2F 35 3B    Robert Weber
3D 43 47 49 4F 53 59 61 65 67 6B 6D 71 7F 83    UnixOps/ITS UCB
89 8B 95 97 9D A3 A7 AD B3 B5 BF C1 C5 C7 D3    Univeristy of Colorado
--------

> 
> On Mon, 03 Nov 2003 13:05:24 -0700
> "Robert Weber" <address@hidden> wrote:
> > I just went to do a restore on a mirror that has been error free for months
> > and discoverd several file had not been updated.  I dug up the error logs
> > and found THOUSANDS of lines like:
> > 
> > librsync: ERROR: (rs_file_copy_cb) seek failed: Invalid argument
> > librsync: ERROR: (rs_job_complete) patch job failed: IO error
> > UpdateError cos/CEDAR/cedar.pro librsync error 100 while in patch cycle
> > 
> > And for every one the file was not updated.  I was running 0.12.4 and librs
ync
> > 0.9.6.  I upgraded to 0.12.6 but I don't know if this will fix it and I
> > wanted to hit the list first.  
> 
> The not updating part is actually the intended behavior for this type of
> thing, see the error policy at
> http://rdiff-backup.stanford.edu/error_policy.html.
> 
> Of course, UpdateErrors are tolerated like this because they are
> supposed to arise only when the file is changing as rdiff-backup is
> processing it.  Is it possible this was the case with
> cos/CEDAR/cedar.pro and the other files?
> 
> If not, it looks like an internal librsync error, possibly because
> librsync can't read or seek around in the file.  So upgrading to 0.12.6
> probably won't fix it.
> 
> 
> -- 
> Ben Escoto
> 
> --Za=.QDpl_Q6L7MTk
> Content-Type: application/pgp-signature
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iD8DBQE/pxI++owuOvknOnURAhkdAJ9KNpg3jWvPXYHtdtxlMWrPDFCXIQCfW2TU
> mgvl2EMsBBp//bq38UgZhR0=
> =YgxK
> -----END PGP SIGNATURE-----
> 
> --Za=.QDpl_Q6L7MTk--
> 
> 
> 
> --===============0174799030==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> rdiff-backup-users mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/rdiff-backup-users
> 
> --===============0174799030==--
> 
> 

--------

----------
Status: by weberr Tue Nov  4 09:52:12 2003
----------