Has anyone looked at the problem when working on files larger than
25Gig? Previous messages about this problem were titled "error 107" and
"librsync error 107 while in patch cycle" it looks like a problem with
librsync. I get this error
python: ERROR: (rs_job_iter) internal error: job made no pr
is this with librsync 0.9.6 or librsync 0.9.7? 0.9.6 has known problems
with files >= 4GiB.
also if it's linux you need to ensure that everything is built with
-D_FILE_OFFSET_BITS=64 (which it typically is on recent enough distros).
-dean
On Fri, 29 Apr 2005, Clint Silvester wrote:
> Has any
dean gaudet wrote:
>is this with librsync 0.9.6 or librsync 0.9.7? 0.9.6 has known problems
>with files >= 4GiB.
>
>also if it's linux you need to ensure that everything is built with
>-D_FILE_OFFSET_BITS=64 (which it typically is on recent enough distros).
>
>-dean
>
>On Fri, 29 Apr 2005, Clin
May I suggest that you might want to try some other technique for
backing up
a 25 gig file?
Maybe using LVM and "snapshot" techniques. I cannot say that I've
ever
implemented them myself, but it would seem to be a better way of being
able to get a consistant backup of a file that could cha
> Clint Silvester <[EMAIL PROTECTED]>
> wrote the following on Mon, 02 May 2005 19:26:59 -0600
> I've just recompiled making sure the whole thing used
> -D_FILE_OFFSET_BITS=64 by running CC="gcc -D_FILE_OFFSET_BITS=64"
> ./configure --prefix=/usr etc. and still after testing this i got
> t
On Mon, 2 May 2005, Clint Silvester wrote:
> This is with 0.9.7, but I don't see it using that in any of the gcc
> commands when it's compiling. The configure script says
>
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for la
Clint Silvester wrote:
Has anyone looked at the problem when working on files larger than
25Gig? Previous messages about this problem were titled "error 107" and
"librsync error 107 while in patch cycle" it looks like a problem with
librsync. I get this error
I have a client where we do backups o
Just a little stupid check:
Make sure your destination filesystem can handle such files. (Of course you
already might have checked this)
Am Dienstag 03 Mai 2005 03:26 schrieb Clint Silvester:
> dean gaudet wrote:
> >is this with librsync 0.9.6 or librsync 0.9.7? 0.9.6 has known problems
> >with
