[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rdiff-backup-users] Failing backup: Long int too large to convert t
From: |
Thomas Jarosch |
Subject: |
Re: [rdiff-backup-users] Failing backup: Long int too large to convert to int |
Date: |
Fri, 3 Apr 2009 09:25:57 +0200 |
User-agent: |
KMail/1.11.0 (Linux/2.6.27.19-78.2.30.fc9.i686; KDE/4.2.1; i686; ; ) |
Hello Andrew,
On Thursday, 2. April 2009 14:02:27 Andrew Ferguson wrote:
> I'm quite positive that is a bug in the gzip support shipped with
> Python 2.2.x which was fixed in Python 2.3.x. That version of the gzip
> interface could not handle files > 2GB.
>
> So, the best solution is to upgrade Python, at least to 2.3.x. If that
> is not feasible, then you can use --no-compression to disable
> compression on your increment files, which will avoid this bug. Or,
> you can use an --exclude rule to not backup files > 2GB.
Thanks a lot! The --no-compression option did the trick.
The server will be upgraded later this year.
> If you want to confirm that this is the case, then you can use the -v5
> option to rdiff-backup, which will tell you the name of each file that
> it is working on. The last file it is working on before this error
> should be > 2GB.
Thanks, too, hopefully I won't need that ;-)
Have a nice weekend,
Thomas