From owner-freebsd-current@FreeBSD.ORG Mon Sep 14 15:57:45 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 640C0106566C for ; Mon, 14 Sep 2009 15:57:45 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2E58FC16 for ; Mon, 14 Sep 2009 15:57:44 +0000 (UTC) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 620CB19E023; Mon, 14 Sep 2009 17:57:43 +0200 (CEST) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 4D15319E019; Mon, 14 Sep 2009 17:57:41 +0200 (CEST) Message-ID: <4AAE67F4.4050001@quip.cz> Date: Mon, 14 Sep 2009 17:57:40 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: Mike Tancsa 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> In-Reply-To: <200909141526.n8EFQwuG021801@lava.sentex.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: ata timeouts under load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2009 15:57:45 -0000 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 error=4 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