Hi Kevin
> -----Original Message-----
> From: Kevin Brown [mailto:kevin@sysexperts.com]
> Sent: 17 April 2003 03:35
> To: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] pg_clog woes with 7.3.2 - Episode 2
>
> I'd also start looking carefully through the system logs for
> SCSI errors. You should see some if you're getting bad block
> problems (in particular, you should see bad block remapping
> attempts that couldn't read the data from the original bad
> block -- this, or running out of spare blocks, is the only
> reason you should see errors at all on an otherwise functional setup).
No errors on the system at all apart from PostgreSQL. On the previous
disk, the number of errors reported by badblocks was rising from 64
initially to 80-something when I took it out.
> If badblocks shows errors but you don't see any SCSI errors
> in the system logs, then it's time to start suspecting the
> disk controller or perhaps even the PCI bus controller,
> because it means something really weird is happening on the
> backend that is entirely invisible. Cabling or termination
> could be an issue, but I'd expect to see parity errors, timed
> out commands, etc. if that's the problem.
Yes, me too. Still, I've now tried a 29160N adaptor, and changed the
cable to a DPT one (both that and the previous Adaptec have hardwired
terminators). I've also removed the DAT drive from the system so the
only things on the SCSI bus are 2 identical disks and the adaptor.
I'm beginning to wonder about my shiny new 2.4.20 kernel...
Regards, Dave.
