From owner-freebsd-hackers  Sun Feb 25 02:50:52 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA25357
          for hackers-outgoing; Sun, 25 Feb 1996 02:50:52 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA25352
          Sun, 25 Feb 1996 02:50:51 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id CAA10670; Sun, 25 Feb 1996 02:50:42 -0800 (PST)
Message-Id: <199602251050.CAA10670@ref.tfs.com>
Subject: Re: wierd scsi error message
To: hsu@freefall.freebsd.org (Jeffrey Hsu)
Date: Sun, 25 Feb 1996 02:50:42 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: hackers@freefall.freebsd.org
In-Reply-To: <199602242300.PAA25652@freefall.freebsd.org> from "Jeffrey Hsu" at Feb 24, 96 03:00:17 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> 
> 
> Okay, now that I know what the message means, the $24,000 question is how
> do I identify the file for which this write failed?
> 
> Feb 24 02:24:15 armour /kernel: sd0(uha0:0:0): Deferred Error: HARDWARE FAILURE 
> info:327900 asc:3,0 Peripheral device write fault field replaceable unit: 11 sks:80,19
> 
> 
The error occured during an operation for which a successful
status had already been returned to the driver.. I would guess that
this was a write-behind operation and that teh write could not succeed.
Asa guess the AWRE (or whatever it is) bit was not set in hte drive
config, otherwise it should have silently remapped the bad block.
(unless it wasn't a media error).
Probably the info field contains the block number that
was being written (in absolute numbers). I don't know the base off hand
(16 or 10) I guess 10.