From owner-freebsd-questions@FreeBSD.ORG Wed Aug 31 23:25:22 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FD14106566B for ; Wed, 31 Aug 2011 23:25:22 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 7F3418FC0C for ; Wed, 31 Aug 2011 23:25:22 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p7VNPLEc070356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Aug 2011 16:25:21 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p7VNPLLn070355; Wed, 31 Aug 2011 16:25:21 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA26205; Wed, 31 Aug 11 16:23:05 PDT Date: Wed, 31 Aug 2011 23:22:59 -0700 From: perryh@pluto.rain.com To: bonomi@mail.r-bonomi.com, basarevych@gmail.com Message-Id: <4e5f24c3.agV2UHzbjHEXght8%perryh@pluto.rain.com> References: <201108311826.p7VIQRCY068730@mail.r-bonomi.com> In-Reply-To: <201108311826.p7VIQRCY068730@mail.r-bonomi.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Is there way to get filename for specific LBA? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 23:25:22 -0000 Robert Bonomi wrote: > > Aug 31 05:13:24 da kernel: ad6: WARNING - READ_DMA UDMA ICRC > > error (retrying request) LBA=107491647 > > ... I looked at bsdlabel a it's partition f, /home. But what > > is the file name? > > There's *no* easy way to find out. You'll have to grovel through > all the filesystem metadata, and the layers of index blocks for > every file until you find the 'rgiht' one. This is what "icheck -B" was for, but icheck(8) no longer exists and that particular bit of functionality does not seem to be provided in fsck(8). One current userland utility (other than fsck) which does know how to grovel through the metadata and index blocks is dump(8), but you'd have to hack on it to report which inode was using a particular block.