From owner-freebsd-scsi  Mon Oct 28 07:33:39 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA01475
          for freebsd-scsi-outgoing; Mon, 28 Oct 1996 07:33:39 -0800 (PST)
Received: from deacon.cogsci.ed.ac.uk (deacon.cogsci.ed.ac.uk [129.215.144.7])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA01470
          for <freebsd-scsi@freebsd.org>; Mon, 28 Oct 1996 07:33:35 -0800 (PST)
Received: (from richard@localhost) by deacon.cogsci.ed.ac.uk (8.6.10/8.6.12) id PAA23211; Mon, 28 Oct 1996 15:33:32 GMT
Date: Mon, 28 Oct 1996 15:33:32 GMT
Message-Id: <199610281533.PAA23211@deacon.cogsci.ed.ac.uk>
From: Richard Tobin <richard@cogsci.ed.ac.uk>
Subject: Re: SCSI harddisk trouble: MEDIUM ERROR
To: Peter Dufault <dufault@hda.hda.com>
In-Reply-To: Peter Dufault's message of Mon, 28 Oct 1996 09:06:47 -0500 (EST)
Organization: just say no
Cc: freebsd-scsi@freebsd.org
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Here is a sketch of what an "automatic tool" could do.
> I don't think it is worth it, and such a tool may give
> people a false sense of having fixed things that they haven't:

As far as I can see, they *have* fixed things, apart from still having
a damaged file.  Maybe if you add a step

> 5. Write the (probably garbage) data back,
> causing it to reassign the block or at least store the data; 

5.5. Delete the file containing the bad sector (after asking the user,
of course) or move it to lost+found.

> 6. fsck.

Of course, if it's a directory block things are worse.

I'd like such a tool; I have a couple of Syquest removable disks with
bad sectors and wouldn't be surprised to get more.

-- Richard