[rdiff-backup-users] Fwd: Re: Problems with missmatching hashes

[Christian Kölpin]

Hi Maarten

thanks for your quick help. 

You point me in the correct direction. Non of "usual suspects" was the "point 
of failure". Cause anything should have (negative) effects to my BackupSource 
as well. (even the SATA-Link cause i use HatSwap-Bays...).

But this hint points me to hdparm and smartctl. My server is monitored by Munin 
every 5 Minutes. Only files who are that large, to need more than 5 Minutes got 
hit frequently... After turning off this monitoring i create a "valid" backup 
with 1.4T Data (needs nearly 12 hours with checks... so my ram should be fine 
;))

I guess my "consumer" HardDrives got problems if i put them to throughput-limit 
and query them frequently about their status

greetings
Raptor 2101

> -------- Original-Nachricht --------
> Datum: Sun, 17 Jul 2011 00:38:39 +0200 (CEST)
> Von: Maarten Bezemer <address@hidden>
> An: "Christian Kölpin" <address@hidden>
> CC: address@hidden
> Betreff: Re: [rdiff-backup-users] Problems with missmatching hashes
> 
>My first guess would be bad ram. Run memtest86+ for at least 12 hours (or 
>less if it reports problems, no point in testing bad ram for more errors).
>
>Other things to check would be your power supply, the timings for cpu, 
>ram, and bus, or ide/sata cables and connections.
>
>You could also try to find reports of other people getting corruption or 
>instability issues with your type of mainboard, chipset, ram, etc. I've 
>had timing issues with Via chipsets in the past, that didn't show up in 
>memtest, but got several faulty md5sums of a 100MB file when repeatedly 
>checking it. Underclocking the ram to match cpu core speed solved that 
>issue. (Happened consitently with several mainboards and several brands >of 
>ram, my ram was fine...)
>
>
>If you don't get memtest errors, report back here with some more info 
>about your hardware.
>
>Memtest can be downloaded at: www.memtest.org
>
>
>Hope this helps..
>
>-- 
>Maarten