From owner-freebsd-hackers@FreeBSD.ORG  Sat Feb 18 17:22:42 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 AB41D16A420
	for <hackers@freebsd.org>; Sat, 18 Feb 2006 17:22:42 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6FCBD43D75
	for <hackers@freebsd.org>; Sat, 18 Feb 2006 17:22:37 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k1IHLR5W053530
	for <hackers@freebsd.org>; Sat, 18 Feb 2006 10:21:27 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Sat, 18 Feb 2006 10:21:45 -0700 (MST)
Message-Id: <20060218.102145.26324437.imp@bsdimp.com>
To: hackers@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(harmony.bsdimp.com [127.0.0.1]);
	Sat, 18 Feb 2006 10:21:27 -0700 (MST)
Cc: 
Subject: Bad block -> file mapping
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2006 17:22:42 -0000

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...

Warner

P.S.  Here's a sample report:

Num  Test_Description    Status           LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure     8949         65818210
# 2  Short offline       Completed without error     8948         -