Xref: utzoo comp.sys.att:4072 unix-pc.general:1293
Path: utzoo!utgpu!water!watmath!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ucsbcsl!comdesign!ivucsb!todd
From: todd@ivucsb.UUCP (Todd Day <todd>)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Reading Hard Drive Blocks
Message-ID: <253@ivucsb.UUCP>
Date: 25 Aug 88 14:31:26 GMT
Organization: The Audio Club at UCSB, Isla Vista, California
Lines: 20

I recently enquired about removing a bad block that sometimes shows up
in my unix.log.  Well, I suspect that my bad block has something to do
with the uucp stuff, as the error times always seem to coincide with
some item in /usr/spool/uucp/LOGFILE.  If I get rid of this bad block
it could be catastrophic to my mailing system.

I was wondering if there is some way to go out and actually read the block
before I delete it, so I can see what it is and prepare for its removal.
Actually, what I was really thinking of doing was renaming whatever file
it happened to be in to file.old and copy it to itself.

Another thing I was wondering is what causes soft errors.  I mean, how
does the computer recover from something like a bad hard disk read?

Thanks in advance.

-- 
   /| Todd Day (805)968-9352 |\    "I asked for a car, I got a computer.  How's
+-+ | The Audio Club at UCSB | +-+    that for being born under a bad sign?"
+-+ |  926 B Camino Del Sur  | +-+      comdesign!ivucsb!todd@pyramid.com
   \| Isla Vista, CA   93117 |/        {sun}!pyramid!comdesign!ivucsb!todd