Date: Sun, 27 Feb 2005 16:53:44 +0100 From: cpghost@cordula.ws To: freebsd-questions@freebsd.org Subject: Re: WRITE_DMA errors on SATA drive under 5.3-RELEASE Message-ID: <20050227155344.GA78232@bsdbox.farid-hajji.net> In-Reply-To: <1561762673.20050227155330@wanadoo.fr> References: <1561762673.20050227155330@wanadoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050227155344.GA78232>