In all likelihood, your problem is caused by hardlinked files in
your backup. The --verify and --compare-hash directives in
version 1.2.8 have problems with such files.
You might take a look at bug report #26848:
https://savannah.nongnu.org/bugs/?26848
I have just now updated the report with
On 08/10/2010 04:16 PM, Robinson, Eric wrote:
It's quiet.
Yeah, too quiet. Gives me the willies.
Me, too.
--
Eric Robinson
-Original Message-
From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
EHLO
Greetings,
devels: rdiff-backup stores data by using industry standard gzip. But
bz2 has better compression. Or even usage of 7zip, which is not
industry standard but everyone is using it, so it will become industry
standard sooner or later, and it has more aggressive compression than
all
It's quiet.
Yeah, too quiet. Gives me the willies.
Me, too.
--
Eric Robinson
-Original Message-
From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
On Behalf Of Robinson, Eric
Sent: Saturday,
Lol, hi Eric.
Looks like no-one has any ideas and I've never tried using --compare-hash.
Also now I'm too scared to cause if I see errors they will worry me and
I will want to fix them when there may be not much wrong lol.
There has been a lot of talk in the past about how to verify backups and
I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive.
First I get tons of these messages...
Warning: Metadata file has no digest for file, unable to
compare.
That's scary enough by itself. But then at the end it says...
