Return-Path: <sommerfeld@orchard.arlington.ma.us>
Received: from pacific-carrier-annex.mit.edu by po11.mit.edu (8.9.2/4.7) id AAA27606; Mon, 20 May 2002 00:03:07 -0400 (EDT)
Received: from stack.hamachi.org (sommerfeld.ne.client2.attbi.com [66.31.126.43])
	by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id AAA20720;
	Mon, 20 May 2002 00:02:26 -0400 (EDT)
Received: from syn.hamachi.org (orchard.hamachi.org [18.101.2.2])
	by stack.hamachi.org (Postfix) with ESMTP
	id 6B29F2709; Mon, 20 May 2002 00:02:26 -0400 (EDT)
Received: from syn.hamachi.org (sommerfeld@localhost)
	by syn.hamachi.org (8.11.6/8.8.8) with ESMTP id g4K41OG04862;
	Mon, 20 May 2002 00:01:24 -0400 (EDT)
Message-Id: <200205200401.g4K41OG04862@syn.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Lenny Foner <foner@media.mit.edu>
Cc: marc@MIT.EDU, tytso@MIT.EDU, jmorzins@MIT.EDU, sipb@MIT.EDU
Subject: Re: Which hard disk vendor do you trust? 
In-Reply-To: Message from Lenny Foner <foner@media.mit.edu> 
   of "Sun, 19 May 2002 23:25:11 EDT." <200205200325.XAA07739@out-of-band.media.mit.edu> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 20 May 2002 00:01:23 -0400
Sender: sommerfeld@orchard.arlington.ma.us

> but if it was simply a matter of the drive writing bogus data during
> some "event", it would have spared out the sector and continued.
> This acts like it -can't- spare it out.)

If the drive fails to recover the contents of a sector, it returns an
I/O error to the host software so it knows the data isn't there any
more; a subsequent write will then cause the sector to be spared. 

You get painted into a corner when the host can't overwrite the sector
until it knows what it previously contained ...

When I get the occasional sticky bad sector, I generally get out the
bit tweezers (dd, specifically), overwrite it with zeros, and run an
fsck pass to clean up any dangling pointers.  At least with
BSD-derived filesystems, the main thing I seem to run into is bad
inode blocks -- since they're *always* handled in a read-modify-write
pattern, the "spare-on-write" behavior never gets invoked.

I've seen this sort of thing work on MSCP, SCSI, and IDE disks, under
hp-ux, 4.xbsd on vaxen, and pc's running netbsd.

						- Bill
