Re: [rdiff-backup-users] crash in gzip.py

On Fri, Dec 11, 2015 at 9:56 PM, Lew Wolfgang wrote: > Hi Folks, > > I occasionally encounter an error that terminates a backup > and requires a "--check-destination-dir" run to recover. > > The error seems to be associated with gzip.py being asked to > do a negative

Re: [rdiff-backup-users] crash in gzip.py

On 12/13/2015 04:03 AM, Andrea Cozzolino wrote: On Fri, Dec 11, 2015 at 9:56 PM, Lew Wolfgang > wrote: Hi Folks, I occasionally encounter an error that terminates a backup and requires a "--check-destination-dir" run to

Re: [rdiff-backup-users] crash in gzip.py

On Sun, Dec 13, 2015 at 9:35 PM, Lew Wolfgang wrote: > On 12/13/2015 04:03 AM, Andrea Cozzolino wrote: > > BTW, since rdiff-backup hasn't been updated since 2009, I started to > look around for an alternative. Alas, rdiff-backup's capabilities seem > to be unique. I

Re: [rdiff-backup-users] crash in gzip.py

On 12/13/2015 7:03 AM, Andrea Cozzolino wrote: I have quite the same problem and in the *same* environment (openSUSE 13.2/rdiff-backup 1.2.8). I have a broken and, so far, unrecoverable backup store. Each time I try to backup my home dir, I got a "Negative seek" error while "Writing file

Re: [rdiff-backup-users] crash in gzip.py

On Sun, Dec 13, 2015 at 7:22 PM, Joe Steele wrote: On 12/13/2015 7:03 AM, Andrea Cozzolino wrote: > >> I have quite the same problem and in the *same* environment >> (openSUSE 13.2/rdiff-backup 1.2.8). >> >> I have a broken and, so far, unrecoverable backup store. >> >> Each

Re: [rdiff-backup-users] crash in gzip.py

On 12/13/2015 01:13 PM, Andrea Cozzolino wrote: On Sun, Dec 13, 2015 at 9:35 PM, Lew Wolfgang > wrote: On 12/13/2015 04:03 AM, Andrea Cozzolino wrote: BTW, since rdiff-backup hasn't been updated since 2009, I started to

[rdiff-backup-users] crash in gzip.py

Hi Folks, I occasionally encounter an error that terminates a backup and requires a "--check-destination-dir" run to recover. The error seems to be associated with gzip.py being asked to do a negative seek in write mode. The docs for gzip.py explicitly say it can't do this. I'm not sure about

Re: [rdiff-backup-users] crash with false No space left on device' raised of class error

That seems to have done it; the regress succeeded, and hopefully I can now back-up my computer. Thanks for your help. -Leon On Sat, Nov 9, 2013 at 7:51 AM, Greg Troxel g...@lexort.com wrote: Leon Maurer leon.mau...@gmail.com writes: Howdy, I'm having trouble with rdiff-backup crashing.

Re: [rdiff-backup-users] crash with false No space left on device' raised of class error

Leon Maurer leon.mau...@gmail.com writes: Howdy, I'm having trouble with rdiff-backup crashing. It claims there's No space left on device, which is patently false. The drive is a 2TB drive that's 66% free when rdiff-backup is running: leon@leon-MiniPC:/media/seagate$ df -h | grep seagate

[rdiff-backup-users] crash with false No space left on device' raised of class error

Howdy, I'm having trouble with rdiff-backup crashing. It claims there's No space left on device, which is patently false. The drive is a 2TB drive that's 66% free when rdiff-backup is running: leon@leon-MiniPC:/media/seagate$ df -h | grep seagate /dev/sdc11.9T 604G 1.3T 33%

Re: [rdiff-backup-users] Crash on incremental backup after regression

Hi Dominic, Don't know why but I haven't received your response (have you send it to the list or just to Valerio?). Thanks for the response, I've tried the option but I got a missing arguments error. The manual ( http://rdiff-backup.nongnu.org/rdiff-backup.1.html) doesn't say that

Re: [rdiff-backup-users] Crash on incremental backup after regression

2010/11/26 Dominic Raferd domi...@timedicer.co.uk: It looks to me as if the problem maybe relates to the special characters in the filenames '\xf3' and similar. And I see at the bottom mention of a win_acl. My suggestions are: - try using option --override-chars-to-quote I didn't try this

[rdiff-backup-users] Crash on incremental backup after regression

Hi, Im using rdiff-backup version 1.3.3 on a Windows 2000 server here and the software is crashing on performing a backup. As the previous backups have failed, rdiff-backup makes a regression which seems successful and the, on making the backup itself, the script crashes with the following

Re: [rdiff-backup-users] Crash on incremental backup after regression

It looks to me as if the problem maybe relates to the special characters in the filenames '\xf3' and similar. And I see at the bottom mention of a win_acl. My suggestions are: - try using option --override-chars-to-quote - or - try using option --no-acls - or - try rdiff-backup version 1.2.8.

[rdiff-backup-users] Crash on windows with: [Errno 2] No such file or directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I'm currently using rdiff-backup 1.2.8 on Windows to do my daily backup. It seems like it is crashing on a file with a long path name. Here is the dump of the error: * Shutdown Backup: 2010-04-23

Re: [rdiff-backup-users] Crash in 1.3.3

-users-bounces+craig=plasmatronics.com...@nongnu.org [mailto:rdiff-backup-users-bounces+craig=plasmatronics.com...@nongnu.org ] On Behalf Of Josh Nisly Sent: Friday, 1 May 2009 1:58 AM To: Craig Findlay Cc: rdiff-backup Subject: Re: [rdiff-backup-users] Crash in 1.3.3 CRC check failures typically

Re: [rdiff-backup-users] Crash in 1.3.3

-backup-users-bounces+craig=plasmatronics.com...@nongnu.org [mailto:rdiff-backup-users-bounces+craig=plasmatronics.com...@nongnu.org ] On Behalf Of Josh Nisly Sent: Friday, 1 May 2009 1:58 AM To: Craig Findlay Cc: rdiff-backup Subject: Re: [rdiff-backup-users] Crash in 1.3.3 CRC check failures

Re: [rdiff-backup-users] Crash in 1.3.3

: [rdiff-backup-users] Crash in 1.3.3 CRC check failures typically indicate faulty or dying hardware. JoshN Craig Findlay wrote: Backing up from Unix (OpenBSD) to Unix, both 1.3.3: Cheers, Craig 2009-04-28 09:32:05 Backing up bellfs_backup::/data/home to /mnt/backup/serverbackup/bellfs/home

RE: [rdiff-backup-users] Crash in 1.3.3

=plasmatronics.com...@nongnu.org ] On Behalf Of Josh Nisly Sent: Friday, 1 May 2009 1:58 AM To: Craig Findlay Cc: rdiff-backup Subject: Re: [rdiff-backup-users] Crash in 1.3.3 CRC check failures typically indicate faulty or dying hardware. JoshN Craig Findlay wrote: Backing up from Unix (OpenBSD) to Unix

[rdiff-backup-users] Crash in 1.3.3

Backing up from Unix (OpenBSD) to Unix, both 1.3.3: Cheers, Craig 2009-04-28 09:32:05 Backing up bellfs_backup::/data/home to /mnt/backup/serverbackup/bellfs/home with args: SpecialFileError zopeuser/var/zopectlsock Socket error: AF_UNIX path too long Exception 'CRC check failed' raised of

[rdiff-backup-users] Crash and Traceback from windows version 1.2.6

I am running rdiff-backup v1.2.6 on Windows 64bit XP using this command: rdiff-backup --verbosity 9 --print-statistics C:\Documents and Settings N:\DocSet 1c:\bin\Backup-DocSet.log N: is a USB attached external drive. The traceback, as mangled by cmd window line wrapping, and the head and tail

[rdiff-backup-users] crash rh4 to solaris 8

Dear List, I'm using rdiff-backup to backup my linux and mac boxes with great success. Now I'm trying to include the solaris boxes. Am using the packages from sunfreeware.com. I checked google for need more than 3 values to unpack and found nothing. Any hints? -Aaron. [EMAIL

Re: [rdiff-backup-users] crash rh4 to solaris 8

aurbain wrote: I'm using rdiff-backup to backup my linux and mac boxes with great success. Now I'm trying to include the solaris boxes. Am using the packages from sunfreeware.com. I checked google for need more than 3 values to unpack and found nothing. [EMAIL PROTECTED] desktops]#

Re: [rdiff-backup-users] crash

On Wednesday 04 July 2007, Andrew Ferguson wrote: Neal Becker wrote: rdiff-backup-1.0.5-2.fc7 fedora fc7 x86_64: ending back exception signed integer is greater than maximum of type type 'exceptions.OverflowError': File /usr/lib64/python2.5/site-packages/rdiff_backup/rpath.py,

[rdiff-backup-users] crash

rdiff-backup-1.0.5-2.fc7 fedora fc7 x86_64: ending back exception signed integer is greater than maximum of type type 'exceptions.OverflowError': File /usr/lib64/python2.5/site-packages/rdiff_backup/connection.py, line 334, in answer_request result = apply(eval(request.function_string),

Re: [rdiff-backup-users] Crash due to IOError?

Hi Kristian, On Mon, 4 Dec 2006, [ISO-8859-1] Kristian R�nningen wrote: On a semi-regular basis I'm getting the following error while backing up a certain server, it seems to be some kind of IO-Error (disk or network), and was wondering if there was anything I could do to prevent this. The

[rdiff-backup-users] Crash due to IOError?

Hi, On a semi-regular basis I'm getting the following error while backing up a certain server, it seems to be some kind of IO-Error (disk or network), and was wondering if there was anything I could do to prevent this. The servers are running Debian Sarge, and its rdiff-backup package.

[rdiff-backup-users] Crash whilst regressing file

Hi, I've been running rdiff-backup for a while now to backup a remote server to a local NFS mounted disk. It's all been working fine. But recently a backup failed and any subsequent attempts result in the crash detailed below. I've upgraded both servers to the latest version now but at