From owner-freebsd-questions@FreeBSD.ORG Sat May 26 19:29:17 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFC4D16A421 for ; Sat, 26 May 2007 19:29:17 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id CBEAC13C447 for ; Sat, 26 May 2007 19:29:17 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 6926 invoked from network); 26 May 2007 19:29:17 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 26 May 2007 19:29:17 -0000 Received: from Lowell-Desk.lan (Lowell-Desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id 0FC8128439; Sat, 26 May 2007 15:29:12 -0400 (EDT) Received: by Lowell-Desk.lan (Postfix, from userid 1147) id A21F81D0E1; Sat, 26 May 2007 15:29:11 -0400 (EDT) To: Grant Peel References: <00a701c79ed0$a2c23050$6501a8c0@GRANT> From: Lowell Gilbert Date: Sat, 26 May 2007 15:29:11 -0400 In-Reply-To: <00a701c79ed0$a2c23050$6501a8c0@GRANT> (Grant Peel's message of "Fri\, 25 May 2007 09\:28\:51 -0400") Message-ID: <44k5uvfkoo.fsf@Lowell-Desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Disk Error - DUMP output. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 19:29:18 -0000 "Grant Peel" writes: > Is there any way to figure out the files that are not being read using the DUMP error output below? > > DUMP: read error from /dev/da0s1g: Input/output error: [block 42718592]: count=8192 > DUMP: read error from /dev/da0s1g: Input/output error: [sector 42718594]: count=512 > DUMP: read error from /dev/da0s1g: Input/output error: [block 42671366]: count=5120 > DUMP: read error from /dev/da0s1g: Input/output error: [sector 42671371]: count=512 I had such a problem just last night. I tracked it down by copying directory trees within the filesystem to /dev/null until one failed. Then I repeated the process one directory level down, narrowing down the problem. [It turned out to be my wife's incoming mail spool...]