From owner-freebsd-questions@FreeBSD.ORG Sun Feb 27 14:53:33 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 150E516A4CE for ; Sun, 27 Feb 2005 14:53:33 +0000 (GMT) Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id C687343D54 for ; Sun, 27 Feb 2005 14:53:32 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0909.wanadoo.fr (SMTP Server) with ESMTP id 809052400122 for ; Sun, 27 Feb 2005 15:53:31 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf0909.wanadoo.fr (SMTP Server) with ESMTP id 65137240011D for ; Sun, 27 Feb 2005 15:53:31 +0100 (CET) X-ME-UUID: 20050227145331414.65137240011D@mwinf0909.wanadoo.fr Date: Sun, 27 Feb 2005 15:53:30 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1561762673.20050227155330@wanadoo.fr> To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: WRITE_DMA errors on SATA drive under 5.3-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 14:53:33 -0000 I've gotten two messages like the ones below today on my production server (5.3-RELEASE): messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=4848803 messages:Feb 27 14:48:17 freebie kernel: ad10: FAILURE - WRITE_DMA timed out What do these messages mean? The referenced drive is one of two identical SATA drives on the server; it holds /tmp and /var. I don't recall seeing these messages before. Is there a way to work backwards from the LBA to the filesystem so that I can see which file was being referenced when this occurred? -- Anthony