It seems Andrew Gallatin wrote:
These are UDMA CRC errors, if you upgrade to the latest current, ata
knows to retry these, only if they persist, something is wrong.
However it could indicate cable problems, ie bad connectors or maybe
too long cables..
He said the disk was
It seems [EMAIL PROTECTED] wrote:
Will the backdown to PIO mode be permanent till the next reboot of the
machine, or will the driver be able to attempt to return to DMA mode after
a timeout period. I'm only seeing these errors under really heavy disk
activity (mutlitple nfs readers and
Soren Schmidt writes:
It seems Andrew Gallatin wrote:
These are UDMA CRC errors, if you upgrade to the latest current, ata
knows to retry these, only if they persist, something is wrong.
However it could indicate cable problems, ie bad connectors or maybe
too long cables..
Andrew Gallatin writes:
Soren Schmidt writes:
I've fixed it here (I hope), and it will be in the next batch of fixes.
I hope to get through my mailbox today :)
Thanks. I'm running a kernel built with them now. If/when we see CRC
errors, I'll let you know what happens. We
It seems [EMAIL PROTECTED] wrote:
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
Soren Schmidt writes:
It seems [EMAIL PROTECTED] wrote:
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
Will the backdown to PIO mode be permanent till the next reboot of the
machine, or will the driver be able to attempt to return to DMA mode after
a timeout period. I'm only seeing these errors under really heavy disk
activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the
vinum
