Date: Mon, 14 Sep 2009 17:57:40 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Mike Tancsa <mike@sentex.net> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: ata timeouts under load Message-ID: <4AAE67F4.4050001@quip.cz> In-Reply-To: <200909141526.n8EFQwuG021801@lava.sentex.ca> References: <4AAD4E51.5060908@FreeBSD.org> <4AAD5365.5000902@FreeBSD.org> <4AAD5DD2.4030104@FreeBSD.org> <20090914100941.0adc00aa@Nokia-N810-43-7> <4AAE5F7E.4050103@quip.cz> <200909141526.n8EFQwuG021801@lava.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Tancsa wrote: > At 11:21 AM 9/14/2009, Miroslav Lachman wrote: > > >> I have very similar problem with one disk in gmirror, but it is on 7.2 >> not current. > > >> Sep 14 04:48:29 jimi kernel: ad6: timeout waiting to issue command >> Sep 14 04:48:29 jimi kernel: ad6: error issuing FLUSHCACHE command >> Sep 14 04:48:29 jimi kernel: ad6: TIMEOUT - READ_DMA48 retrying (1 >> retry left) LBA=447001516 >> Sep 14 04:48:29 jimi kernel: ad6: FAILURE - READ_DMA48 >> status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=447001516 > > > Are you sure this is not just a bad cable ? I have had similar symptoms > which was a result of a bad cable. If possible, swap the cable between > the 2 disks and see if it follows the cable. I know it can be caused by bad cables, but everytime I see it with bad cables, it was without "timeout waiting to issue command" and "error issuing FLUSHCACHE command". It was just "TIMEOUT - READ_DMA48..." and similar messages (on different machines in the past). The messages above is from server running for a year without problems, but disk load is higher and filesystem space is more used then before. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AAE67F4.4050001>