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

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

Re: [rdiff-backup-users] Q. on max-file-size behavior


From: Whit Blauvelt
Subject: Re: [rdiff-backup-users] Q. on max-file-size behavior
Date: Sat, 13 Mar 2010 17:47:44 -0500
User-agent: Mutt/1.5.20 (2009-06-14)

On Sat, Mar 13, 2010 at 09:41:34PM +0100, Jernej Simončič wrote:

> > 1. It looks like rdiff-backup can copy a 16.24g file over once, but then
> > insists on performing some impossible calculation on it even if subsequently
> > asked to ignore large files.
> 
> AFAIK, you need to patch librsync to get support for files larger than
> 4GB.

I see the note on the rdiff-backup site pointing to this:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355178

which is a bit old, but, okay Ubuntu 8.04 is at librsync 0.9.7-1build1,
yeah, that would be it then.

Which makes the question be why rsync itself, when compiled from the latest
3.0.7 source (believe that doesn't use the lib), fails even worse with the
16.24g file.

But it also leaves the small bug in rdiff-backup that if a large file has
already been copied in a previous pass, and then the --max-file-size is set
smaller, rdiff-backup insists on doing some sort of process on the prior
large file, which puts it into a seemingly endless loop on that, rather than
simply saying "It's larger than the flag," and moving on.

Or does the bug break even checking the file size as given by the file
system? That, if the bug's still in rsync 3.0.7, would explain why that too
chokes on the file when its --max-size has been set smaller, even when the
file's never been copied over before. Even the broken rdiff-backup can copy
it once (although quite slowly). 

Whit




reply via email to

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