From owner-freebsd-questions@FreeBSD.ORG Mon Feb 28 01:27:39 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 7D98816A4D3 for ; Mon, 28 Feb 2005 01:27:39 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E859743D31 for ; Mon, 28 Feb 2005 01:27:38 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j1S1Rbgd019416 for ; Sun, 27 Feb 2005 20:27:37 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <1561762673.20050227155330@wanadoo.fr> References: <1561762673.20050227155330@wanadoo.fr> Date: Sun, 27 Feb 2005 20:27:36 -0500 To: freebsd-questions@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.2 Subject: Re: WRITE_DMA errors on SATA drive under 5.3-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 01:27:39 -0000 At 3:53 PM +0100 2/27/05, Anthony Atkielski wrote: >I've gotten two messages like the ones below today on my >production server (5.3-RELEASE): > >... kernel: ad10: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D48488= 03 >... 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? =46irst question: which SATA controller are you using? And what is the make&model of the hard drives that you are using? Note: There have been several different threads on different mailing lists from users having WRITE_DMA errors similar to this. At least some of the problem is in the code which handles disk I/O. The developer who works the most on that code is in the middle of a fairly major set of improvements to it, as is described in the thread with a subject of: UPDATE2: ATA mkIII first official patches - please test! on the freebsd-current and freebsd-stable mailing list. That major set of improvements is still being tested, but it does solve some ATA/SATA issues for many users. Which issues you are running into will depend on which SATA controller you have, and the make&model of SATA hard-disks that you have attached to the controller. I realize that none of that info really helps you right now, but I just thought I would say that it may be you're not having any hardware problems. Or at least, not on the disk itself. It might be a problem with the disk-controller, or it might be fairly minor timing-problems that come up under certain kinds of load. Of course, it still *could* be your hard disk... Also note that I am not an expert on hard disks or disk I/O. It's just that I've suffered through many similar problems, and I know that S=F8ren has been working on the newer, improved code for handling ATA/SATA. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu