Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!zehntel!hplabs!sdcrdcf!sdcsvax!dcdwest!ittvax!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!dave@RIACS.ARPA
From: David L. Gehrt <dave@RIACS.ARPA>
Newsgroups: net.unix-wizards
Subject: Re: UDA50 and bad block forwarding
Message-ID: <7795@brl-tgr.ARPA>
Date: Tue, 29-Jan-85 03:17:05 EST
Article-I.D.: brl-tgr.7795
Posted: Tue Jan 29 03:17:05 1985
Date-Received: Sat, 2-Feb-85 13:50:06 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 12


There is a flag mentioned in the mscp header file in 4.2

#define	M_UF_REPLC 0100000 /* Controller initiated bad block replacement */

(sys/vax/mscp) which seems to imply that the controller will do bad
block on its own.  I don't know what that means.  VMS goes through a
very elaborate tap dance with the controller to accomplish "host
initiated bad block replacement."  The work done in this tap dance
implies that bad block reports (a bad block report is *not* just any
hard error, it is an end message flag with the M
----------