Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Thanks, I first dismissed the possibility of faulty hardware because both servers were bought only a few months ago, but after this second crash, I'm getting worried. I'm going to test the RAM with MemTest86+ and see what I can do about the disks. Both servers are Dell PowerEdge 1950 III with 4GB of Fully Buffered RAM, (which I think should correct small errors) and three SAS HDD in RAID 1 (well, two in RAID 1 and one hot-spare) on a (real) hardware RAID card with 256MB of battery-backed cache (PERC 6i). Power supplies are redondant and hooked up to a filtered UPS. Florian Haas wrote : > Eric, > > have you considered the possibility that drbdadm verify is doing exactly > what it's supposed to do, namely detect on-disk errors that may have > been caused by hardware malfunction, driver bug, or RAM corruption? > > And yes, you may want to enable data-integrity-alg to see if you can > catch that corruption, if it exists, in flight. > > Cheers, > Florian > > Eric Marin wrote: >> Hello and sorry about the length of this report, >> [...] >