Re: [rdiff-backup-users] Running out of /tmp space when regressing large files

[dean gaudet]

there's several threads like this in the archive...

unfortunately there's no perfect solution... it needs improvement in the 
code.  (patches welcome :)

note that rdiff-backup at best is going to need 2x the storage space for a 
large file -- otherwise it would be modifying the file in-place and that's 
got crash-safety issues that are just not fun to worry about.

-dean

On Fri, 21 Jul 2006, Jim C. Nasby wrote:

> While attempting to regress a large virtual PC file, rdiff-backup was
> returning an out-of-space error on the server. Turns out /tmp was
> filling up, even though there were no files to be found. Symlinking
> $TEMP (which is /tmp/decibel) to /var/tmp/decibel has moved the issue to
> /var (which in this case will have enough room... for now).
> 
> What is it that's being created in $TEMP, and why doesn't it show up
> under ls? And how can I disable this, since at some point in the future
> I'll have files too large for this to work on...
> -- 
> Jim C. Nasby, Database Architect                address@hidden 
> Give your computer some brain candy! www.distributed.net Team #1828
> 
> Windows: "Where do you want to go today?"
> Linux: "Where do you want to go tomorrow?"
> FreeBSD: "Are you guys coming, or what?"
> 
> 
> _______________________________________________
> rdiff-backup-users mailing list at address@hidden
> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
>