On 28/10/2011 11:03, john wrote: Hi
The same problem as described here strucked me, too: When regressing a backup, rdiff-backup starts instantly consuming memory at quite a high rate, until it reaches 3GB. Then it dies with a memory allocation error, because it is running on a 32bit system.
As this means that I cannot make any new backups now, without starting from scratch, I searched quite a while for a solution to this. But only found this mailing list thread. Does this mean it is a rare error condition?
The system to backup is not that big: 2,2 Million files, 400GB.
Any hints for debugging?
I tested rdiff-backup V1.2.8-r1 and V1.3.3.
cu
John
How much space is there in your /tmp folder? Try specifying a different tmp folder with --local-temp or --remote-temp (i.e. one with massive storage available). Or try increasing the size of your swap location?
(rdiff-backup is supposed to use temp folders as specified here under 'tempdir' but I think it doesn't follow this logic, or at least not reliably. However forcing a specific temp location with --local-temp or --remote-temp does seem to work.)
Dominic
