Re: [Fwd: [Duplicity-talk] SHA1 hash mismatch]

[Kenneth Loafman]

The error message means that the stored hash of the file does not match
the calculated hash.  This indicates a damaged file.  It's possible that
the hash failed because of a bad transfer.  If you verify again, is it
always on the file:
  duplicity-full.2008-05-11T03:52:23+02:00.vol7.difftar.gpg
or does it change to a different file on each verify?  If its the same
file each time, it may have been damaged during the send.

I noted that you were running frequent incrementals (hourly).  Is it
possible that the verify was running at the same time?  Is it possible
that two backups were running at the same time?

Do you have access to SSH for file transfer?  If so, that has built in
protections for network errors.  You might want to try that.

...Ken

Edgar Soldin wrote:
> the log is attached, the full duplicity call is in the last line ..
> seems like the full backup is damaged or tampered. right? But what
> exactly does the error message mean?
> 
> regards ede
> -- 
>> Have you tried running 'duplicity cleanup <target>' to see if there's
>> something there that should not be?
>>
>> If it still persists, run it with -v9 and post the first 100 lines
>> (including the complete command line), and the last 100 lines.
>>
>> ...Ken
>>
>> Edgar Soldin wrote:
>>  
>>> .. unfortunately the problem seems to persist.. it just occurs later on
>>>
>>> any ideas? ..ede
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> Subject:
>>> [Duplicity-talk] SHA1 hash mismatch
>>> From:
>>> Edgar Soldin <address@hidden>
>>> Date:
>>> Mon, 12 May 2008 23:37:48 +0200
>>> To:
>>> Discussion of the backup program duplicity <address@hidden>
>>>
>>> To:
>>> Discussion of the backup program duplicity <address@hidden>
>>>
>>>
>>> Hi all,
>>>
>>> today I had during a verify run..
>>>
>>> Last full backup date: Sun May 11 03:52:23 2008
>>> Invalid data - SHA1 hash mismatch:
>>> Calculated hash: b4dcc344247bb22354fe9dc152cb7c9be6ad7ff7
>>> Manifest hash: 737ea126d69132ebdbabbbbd88fdc9044301d7ba
>>>
>>> unfortunately _only_ during verify .. incremental backup did not
>>> complain at all. Manually deleting a suspicious set of backup files
>>> (manifest was smaller) solved the error.
>>>
>>> But still.
>>> 1. What does it mean?
>>> 2. And why does duplicity not detect or solve it during incremental
>>> backup?
>>>
>>> Regards ede
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>     
>>
>>
>>  
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>   
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk

signature.asc
Description: OpenPGP digital signature