Once the errors start happening, they keep happening at the same place
over and over again. However, if I stop INN, umount the drive, mount
the drive, and start INN, everything is happy (I had it giving me the
above error twice everytime I tried to tell INN to "go"). Since I
umounted the drive and remounted it, it has been running just fine for
~24 hours. That doesn't seem like hardware to me.
> The fact that ext2fs can't find anything wrong does tend to suggest
> that it is indeed a bit-flip error when the blocks are coming off
> disk. It could also be a memory problem, but either way it's more
> symptomatic of system trouble rather than software trouble.
>
> In my case, switching the two disks (history and spool) onto separate
> controllers fixed the problem entirely.
I already have three 1 gig drives on an Adaptec 2940 (one for OS, swap,
and INN; one for history; and one for overviews). The news spool is
five 2 gig drives in a RAID 0 array on a DPT 3224. I have also had the
problem on the 1 gig drives drives, although not in the last week or two.
These are all drives, cables, and adapters that have worked fine for six
months. And yes, the case is well cooled (we have a thermometer on it
that I check every day or two), so I don't think the drives are all
going bad from heat at the same time.
-- Chris Adams - cadams@ro.com System Administrator - Renaissance Internet Services