From owner-freebsd-hackers  Mon Sep 25 15:50:06 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA27892
          for hackers-outgoing; Mon, 25 Sep 1995 15:50:06 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA27887
          ; Mon, 25 Sep 1995 15:50:04 -0700
Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id PAA08301; Mon, 25 Sep 1995 15:49:57 -0700
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199509252249.PAA08301@ref.tfs.com>
Subject: Re: disk going bad?
To: hsu@freefall.freebsd.org (Jeffrey Hsu)
Date: Mon, 25 Sep 1995 15:49:56 -0700 (PDT)
Cc: julian@freefall.freebsd.org, hackers@freefall.freebsd.org
In-Reply-To: <199509250650.XAA03637@freefall.freebsd.org> from "Jeffrey Hsu" at Sep 24, 95 11:50:11 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 426       
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

It only replaces it if it can recover the data..
try writing to that block.. then it should replace it..

> 
> 	Under 2.0.5, run the sample script in the scsi(8 or 1) man page
> 	to turn on bad-block remapping
> 
> I did this and found Auto Read Reallocation was already on.
> 
> In theory, how is this supposed to work?  If the drive replaces the
> bad read block w/ a good block, how does the fs handle the lost
> data?
>