From owner-freebsd-questions@FreeBSD.ORG Sun Feb 27 15:53: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 B5F5F16A4CE for ; Sun, 27 Feb 2005 15:53:39 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41D6D43D2D for ; Sun, 27 Feb 2005 15:53:39 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from bsdbox.farid-hajji.net (bsdbox [192.168.254.3]) by fw.farid-hajji.net (Postfix) with ESMTP id D62A24BB52; Sun, 27 Feb 2005 16:53:37 +0100 (CET) Date: Sun, 27 Feb 2005 16:53:44 +0100 From: cpghost@cordula.ws To: freebsd-questions@freebsd.org Message-ID: <20050227155344.GA78232@bsdbox.farid-hajji.net> References: <1561762673.20050227155330@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1561762673.20050227155330@wanadoo.fr> User-Agent: Mutt/1.5.6i 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: Sun, 27 Feb 2005 15:53:39 -0000 On Sun, Feb 27, 2005 at 03:53:30PM +0100, Anthony Atkielski wrote: > 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 [...] > 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? Theoretically, one could use 'fsdb -r' in a scripted manner, to generate a mapping of file names to blocks (relative to the partition of the file system you are mapping). Once you have the blocks, you'll need to do so artithmetics to map those blocks to LBA address ranges (perhaps via GEOM or using data in disklabels). Finally, you'll have to locate the range for a particular LBA address and work backwards up to the inode #, and then to the filename(s) that link to that inode. Perhaps there's already a system utility or port for this? It would be really useful! > Anthony Cheers, -cpghost. -- Cordula's Web. http://www.cordula.ws/