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