Jeffrey Hsu stands accused of saying:
> 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 general procedure looks like this :
- obtain the SCSI-2 spec. (gatekeeper.dec.com has a copy somewhere)
- Find out what the 'deferred error' message looks like
- look at, and maybe modify the code to emit the block number (if one is
part of the message)
- use some magic tool (fsdb?) to identify which file inhabits that block.
I'm not sure how many of these steps could be short-circuited by someone
more familiar with the SCSI spec than me.
I'm assuming that you set AWRE and ARRE to 1 using scsi(8) already, and
the error message is still appearing?
]] Mike Smith, Software Engineer email@example.com [[
]] Genesis Software firstname.lastname@example.org [[
]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[
]] realtime instrument control (ph/fax) +61-8-267-3039 [[
]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[