|
| From: | Maarten Bezemer |
| Subject: | Re: [rdiff-backup-users] Hash doesn't match recorded hash |
| Date: | Tue, 15 Nov 2011 11:50:04 +0100 (CET) |
On Tue, 15 Nov 2011, Dominic Raferd wrote:
On 15/11/2011 00:23, Alex Schuster wrote:
Warning: Hash da39a3ee5e6b4b0d3255bfef95601890afd80709 of winXPPro-0.log doesn't match recorded hash db9943d0284382131b553cef380aae99871b0f2e! Any idea what has happened?
Vmware files for a running vm may change while being backed up by rdiff-backup, in which case you don't have a consistent backup. Maybe this is why you have this inconsistent hash warning.
If the contents changed during the rdiff-backup run, it bails out and doesn't save the (inconsistent) increment. So that shouldn't happen.
My guess would be a RAM problem, which is more likely to cause corruption in huge vmware disk images than it is for smaller regular files.
Another known cause for this type of corruption is a Via KT400a chipset when running with DDR400. Memtest won't find any errors, but repeatedly md5summing the same large file will result in wrong checksums every now and then ( < 5% of the cases, so try some 100 times... )
But that kind of hardware should have been retired these days anyway. -- Maarten
| [Prev in Thread] | Current Thread | [Next in Thread] |