From owner-freebsd-hackers  Mon Sep 25 00:45:25 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA04590
          for hackers-outgoing; Mon, 25 Sep 1995 00:45:25 -0700
Received: (from sos@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA04577
          ; Mon, 25 Sep 1995 00:45:23 -0700
Message-Id: <199509250745.AAA04577@freefall.freebsd.org>
Subject: Re: disk going bad?
To: hsu@freefall.freebsd.org (Jeffrey Hsu)
Date: Mon, 25 Sep 1995 00:45:23 -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
From: sos@FreeBSD.org
Reply-to: sos@FreeBSD.org
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 792       
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

In reply to Jeffrey Hsu who wrote:
> 
> 	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?

It doesn't and thats why you get the errors.
What I'm interested in is what kind of controller/disk you are using
since I have a combination that produces these error very predictably
though I seem to be the only one having seen this...


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt  (sos@FreeBSD.org | sos@login.dknet.dk)  FreeBSD Core Team
               So much code to hack -- so little time