On Friday November 4, [EMAIL PROTECTED] wrote:
> I'm resending to this list. Any ideas why md was happily writing to a
> disk that the kernel thought had problems?
It appears that the ide driver didn't tell the md driver that it had
problems.
>
> Oct 27 23:44:58 cbs-server kernel: hdk: status timeout: status=0x80 {
> Busy }
> Oct 27 23:44:58 cbs-server kernel:
> Oct 27 23:44:58 cbs-server kernel: hdk: DMA disabled
> Oct 27 23:44:58 cbs-server kernel: PDC202XX: Secondary channel reset.
> Oct 27 23:44:58 cbs-server kernel: hdk: drive not ready for command
> Oct 27 23:45:04 cbs-server kernel: ide5: reset: master: ECC circuitry
> error
> Oct 27 23:45:04 cbs-server kernel: hdk: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
If md got a failure back from an IO request, it should say:
raid5: Disk failure on kdj, disabling device. ....
The fact that it didn't strongly suggests and error never came
back....
Maybe the PDC202XX driver was retrying lots of times or something.
Sorry I cannot be more helpful.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
