[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] Robustness to errors during backup

From: rdiff
Subject: Re: [rdiff-backup-users] Robustness to errors during backup
Date: Tue, 26 Jun 2007 12:48:26 -0700 (PDT)

On Tue, 26 Jun 2007, address@hidden wrote:

On Tue, 26 Jun 2007, Frederik wrote:

On 6/26/07, Charles Duffy <address@hidden> wrote:
Does --check-destination-dir remove increments on you, or do you get
some kind of error even after using --check-destination-dir?

--check-destination-dir happily crashes:
address@hidden backup]# rdiff-backup --check-destination-dir Luna
Exception 'CRC check failed' raised of class '<type 'exceptions.IOError'>':

We've had this exact problem and there's fixes floating around the mail archives. Basically, find any zero-byte .gz files, in the rdiff-bakcup-data directory, delete 'em, and call --check-destination-dir again.

Is there a developer which can build a test case for creating zero-byte .gz increment files and then build a fix into --check-destination-dir? This is definitely not the first time this has happened. It often happens after a kill -9 of rdiff-backup, or a out-of-disk-space error.

It would be interesting to sprinkle exit(0)'s at various points between io sync()'s in rdiff-backup's code and test its recovery, something akin to the paper "Using Model Checking to Find Serious File System Errors" written for OSDI 2004:


reply via email to

[Prev in Thread] Current Thread [Next in Thread]