rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] Failing on 11GB file - other large files workin


From: Ben Escoto
Subject: Re: [rdiff-backup-users] Failing on 11GB file - other large files working
Date: Tue, 22 Jul 2003 18:21:57 -0700

>>>>> "Ty!" == ty  <Ty!>
>>>>> wrote the following on Tue, 22 Jul 2003 16:00:28 -0600

  Ty!> Hmm...  unfortunatly 12.1 did not fix the problem.  Since you
  Ty!> were able to do it with 12.1 on two totally different
  Ty!> randomized files, I'm guessing that the problem is outside of
  Ty!> rdiff-backup.  Which python version are you running?  Do you
  Ty!> know if there is any way to verify that librsync got compiled
  Ty!> with large file support (my compile, but I've been known to
  Ty!> goof builds once or twice...)?

In rdiff-backup, librsync doesn't actually do any file handling.  Data
is supplied to and read from librsync with python routines.  So the
issue probably is not whether librsync was compiled with large file
support, although there might still be some limiting constant in there
somewhere.

  Ty!> Also, for python and librsync, do you use package versions or
  Ty!> do you compile your own?

I'm using python v2.2.1 that came with redhat 8.0 I think.  librsync I
compiled my own from the old 0.9.5.1 package.  However, the version of
librsync in CVS is much newer and supposedly better, so you may want
to try that.  (In fact, I just upgraded now.  NB: Assuming you are
using a shared library librsync now, remember to ./configure
--enable-shared when you use the CVS version.)

You may also want to try using 'rdiff' directly, to just make a
signature of a large file, try producing a delta of two large files,
and/or patching a large file with a large delta.


-- 
Ben Escoto

Attachment: pgpZ8FLuVNuAY.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]