Thanks for the reply.
Yes I did check the related pages. And I tried to use the Python version
2.6 which I assume should not suffer from the problem. But it does suffer.
At that time, I was using Mac OS 10.6 which is assumed to be 64 bits.
Until recently, test was done with Mac OS 10.8 with Pyth
It looks like you were encountering the python bug identified here:
http://bugs.python.org/issue1747858
Before their fix, the uid was being converted to a (32 bit) signed int,
which, as you have noted, isn't big enough. After the fix, the uid is
converted to a long. I don't know anything abo
After the orignal post, there is no feedback. Recently, I tried to fix
the problem. I didn't know any about Python, started debugging by inserting
print statement. Figured out in the Mac, some times it has file with uid
and gid set to 4294967294 (nobody). It seems Python doesn't accept unsigned
I'm new to the rdiff-backup
I'm running Mac OS 10.6.6, installed the rdiff-backup 1.3.3 and tried
to backup 110GB of data, at around 60GB, it stopped with following error:
Exception 'signed integer is greater than maximum' raised of class '':
File "/Library/Python/2.6/site-packages/rdiff_backup
hi,
manual reply to this:
http://www.mail-archive.com/rdiff-backup-users@nongnu.org/msg04953.html
> But then there's http://bugs.python.org/issue6873, which indicates
> that perhaps lchown still has the problem in the released Python
> versions. If you can figure out how to reproduce it outside
On Sat, 16 Jan 2010 18:11:56 +0100, Michel Le Cocq
wrote:
> File "/usr/local/lib/python2.6/site-packages/rdiff_backup/rpath.py",
> line 973, in chown
> try: self.conn.C.lchown(self.path, uid, gid)
> OverflowError: signed integer is greater than maximum
>
> Michel Le Cocq a écrit:
> >
>
Adrian Klaver a écrit:
> On Sunday 17 January 2010 10:40:17 am Michel Le Cocq wrote:
> > I'm building a virtual machine like my save server.
> >
> > I tried rdiff-backup-devel-1.3.3 and rdiff-backup-1.2.8,1 on this
> > virtual host and I've got the same error
> >
> > So I did :
> >
> > $ pkg_add gc
On Sunday 17 January 2010 10:40:17 am Michel Le Cocq wrote:
> I'm building a virtual machine like my save server.
>
> I tried rdiff-backup-devel-1.3.3 and rdiff-backup-1.2.8,1 on this
> virtual host and I've got the same error
>
> So I did :
>
> $ pkg_add gcc45
> $ pkg_add -r librsync
> $ wget
> ht
I'm building a virtual machine like my save server.
I tried rdiff-backup-devel-1.3.3 and rdiff-backup-1.2.8,1 on this
virtual host and I've got the same error
So I did :
$ pkg_add gcc45
$ pkg_add -r librsync
$ wget
http://savannah.nongnu.org/download/rdiff-backup/rdiff-backup-1.2.8.tar.gz
$ tar
Here is the complete Traceback :
[r...@sauvelipn2009 ~]# rdiff-backup --force -v3 --print-statistics
--force /mnt/users_lipn/export/vol01/jc
/backup/Lipn/users_backup1/export/jc
Exception 'signed integer is greater than maximum' raised of class
'':
File "/usr/local/lib/python2.6/site-packages/rd
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
>> greate
On Jan 5, 2009, at 4:00 PM, Brad Beyenhof wrote:
First of all, I really like rdiff-backup. In most cases (all but the
one I'll detail below), it's been great for me.
Searching in the mailing-list archives has led me to believe that
either the operating system version (64- versus 32-bit) or the
First of all, I really like rdiff-backup. In most cases (all but the
one I'll detail below), it's been great for me.
Searching in the mailing-list archives has led me to believe that
either the operating system version (64- versus 32-bit) or the python
version may be to blame here. The server I'm
13 matches
Mail list logo