From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 18 21:48:53 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8474F16A420 for ; Sat, 18 Feb 2006 21:48:53 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 059AB43D72 for ; Sat, 18 Feb 2006 21:48:52 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (ujngihhm2ph5tgcn@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k1ILmhHc037630; Sat, 18 Feb 2006 13:48:43 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k1ILmgJs037629; Sat, 18 Feb 2006 13:48:42 -0800 (PST) (envelope-from jmg) Date: Sat, 18 Feb 2006 13:48:42 -0800 From: John-Mark Gurney To: "M. Warner Losh" Message-ID: <20060218214842.GG69162@funkthat.com> Mail-Followup-To: "M. Warner Losh" , hackers@freebsd.org References: <20060218.102145.26324437.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060218.102145.26324437.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: hackers@freebsd.org Subject: Re: Bad block -> file mapping X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2006 21:48:53 -0000 Warner Losh wrote this message on Sat, Feb 18, 2006 at 10:21 -0700: > I have a hard disk that's been in service a long time. I recently > installed the SMART monitoring tools. On occasion, I get reports of > LBAs it can't read. I'd like to map the LBA to an actual file in the > file system, if possible. Does anybody have any tools that can help > me with this? > > I know I need to get a new disk. In the mean time, I need to cope > with these errors in a sane manner... ffsrecov will do this for UFS1... I did make ffsrecov compile on 5.x, but w/ the complications of making it support UFS2, I abandoned it.. With a bit of work, ffsrecov.py can be taught this and handle both ufs1 and ufs2... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."