Re: dpt_i2o and i2o_block on amd64 etch
On Mon, May 14, 2007 at 11:56:03AM -0500, C M Reinehr wrote:
> I can't say for sure whether it's i2o_block that's causing the problem, but I
> have a dual-Opteron server that's running up-to-date Etch with md RAID-1. It
> seems that about once a month or so when I check my logs I see that one of
> the md devices has become corrupted and was rebuilt. For example:
>
> Jan 7 01:06:03 eljudnir kernel: block-osm: transfer error
> Jan 7 01:06:14 eljudnir kernel: disk 0, wo:0, o:1, dev:i2o/hdc1
> Jan 7 01:06:14 eljudnir kernel: disk 1, wo:0, o:1, dev:i2o/hdd1
> Jan 7 01:06:18 eljudnir kernel: block-osm: transfer error
> Jan 7 01:13:14 eljudnir mdadm: Rebuild20 event detected on md device /dev/md1
> ...
>
> But, I suppose this also could be the result of a disk drive that is failing
> or any of several other causes.
>
> I'm using i2o_core & i2o_block. It's a Tyan S2882UG3NR Thunder K8S M/B with a
> built-in Adaptec AIC7902W dual-channel U320 SCSI controller.
mdadm runs a raid consistency check once a month, which will likely
appear as a rebuild in the logs, although it is actually just a compare
being done. So maybe that is what it is. Of course the transfer error
seems to indicate it probably isn't.
--
Len Sorensen
Reply to: