Andrew Ferguson-4 wrote: > > > On Jan 5, 2009, at 4:00 PM, Brad Beyenhof wrote: > >> Backing up from the 64-bit system works fine, and two of the >> directories I'm backing up from the 32-bit system are fine as well. >> However, one directory reports "OverflowError: signed integer is >> greater than maximum" and quits partway through the backup. The >> terminal output with the default verbosity is below; I can attach a >> log with a higher verbosity if requested. > > > Hi Brad, > > This is a known problem that is due to a bug in Python. The Python bug > has been fixed in their SVN, and was slated to be a part of 2.5.3, so > it should be included in the latest Python releases: 2.5.4, 2.6.1, and > 3.0. Try upgrading your Python to 2.5.4 or 2.6.1. > > Here is some more information about the problem: > > https://bugs.launchpad.net/ubuntu/+source/rdiff-backup/+bug/245844 > http://bugs.python.org/issue1747858 >
I have the same problem. I'm on python26-2.6.4 with rdiff-backup-1.2.8,1 I just did : # rm -rf /backup/users_backup/toto/rdiff-ba* # rdiff-backup --force /mnt/users/toto /backup/Lipn/users_backup/toto [...] verflowError: signed integer is greater than maximum I'm also on a 64 bit sys : FreeBSD 8.0-RELEASE AMD64 -- Michel -- View this message in context: http://old.nabble.com/OverflowError%3A-signed-integer-is-greater-than-maximum-tp21299282p27187184.html Sent from the rdiff-backup-users mailing list archive at Nabble.com. _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
