I suspect that if you check, you will find that the files listed
in your warning messages have 2 or more hardlinks to them.
After seeing your post, it occurred to me that your problem might
be related to a bug report I filed back in June (and which I have
just now updated):
http://savannah.nongnu.org/bugs/index.php?26848
As noted in the bug report, I suspect that files restored from
your backups will likely end up being hardlinked differently from
the way that they were linked originally.
I had included a patch with the bug report that seemed to fix the
problems I reported. That is to say, future backups could be
made and restored correctly, hardlinks and all. However, the
patch won't help with the restoration of earlier backups from a
repository.
Although I use this patch myself, I would feel a lot better if
the patch was reviewed and blessed by the developers before it
went into widespread use for anything other than testing
purposes. My dabbling with the internals of the rdiff-backup
program has been very limited.
--Joe
On 11/25/2009 4:11 PM, Alex Samad wrote:
Hi
After following the thread on verify times. I have decided to run
--verify on some of my backup repos
and I am getting a lot of
Warning: Cannot find SHA1 digest for file bin/bzcat,
perhaps because this feature was added in v1.1.1
Warning: Cannot find SHA1 digest for file bin/bzip2,
perhaps because this feature was added in v1.1.1
this is against a repo that i just recently ran rdiff-backup against
with no errors.
this is on debian amd64
ii rdiff-backup 1.2.8-5 remote incremental
backup
which looks like the latest version
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
