[EMAIL PROTECTED] writes:
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these errors indicate?
>
> ad5: status=51 error=84
> ad_interrupt: hard error
> vinum0.p0.s3: fatal read I/O error
> ad6: status=51 error=84
> ad_interrupt: hard error
> vinum0.p0.s4: fatal read I/O error
>
> These drives are hanging off this controller;
> ata-pci1: <Promise Ultra/33 IDE controller> irq 9 at device 9.0 on pci0
> ata-pci1: Busmastering DMA supported
These are UDMA CRC errors. Whatever you do, DO NOT upgrade to a
recent current without reading the ata driver's commit logs very
carefully.
The ata-driver has recently grown recovery code where it will try to
back down to PIO mode to fetch such blocks. As recently as last week,
the ata driver would lock a machine solid (unpingable, reset or
power-cycle required) when attempting to back down to PIO mode when
the drive in question was attached to a Promise Ultra controller.
Soren knows about the problem & is going to fix it.
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
