Date: Sat, 26 May 2007 15:29:11 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Grant Peel <gpeel@thenetnow.com> Cc: freebsd-questions@freebsd.org Subject: Re: Disk Error - DUMP output. Message-ID: <44k5uvfkoo.fsf@Lowell-Desk.lan> In-Reply-To: <00a701c79ed0$a2c23050$6501a8c0@GRANT> (Grant Peel's message of "Fri\, 25 May 2007 09\:28\:51 -0400") References: <00a701c79ed0$a2c23050$6501a8c0@GRANT>
next in thread | previous in thread | raw e-mail | index | archive | help
"Grant Peel" <gpeel@thenetnow.com> 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...]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44k5uvfkoo.fsf>