Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!gatech!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: ULTRIX 1.1 Eagle Disc Problems solved - Summary
Message-ID: <3270@umcp-cs.UUCP>
Date: Wed, 19-Feb-86 09:41:21 EST
Article-I.D.: umcp-cs.3270
Posted: Wed Feb 19 09:41:21 1986
Date-Received: Fri, 21-Feb-86 04:24:00 EST
References: <207@ecrcvax.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 23

In article <207@ecrcvax.UUCP> snoopy@ecrcvax.UUCP (Sebastian Schmitz) writes:
>... my SI eagles have 48 sects per track and the MSCP controller
>says they only have 47. Answer: The MSCP *controller* reserves one
>(the last) sector of any track for *its own* bad block forwarding.
>[...]  I presume the general way is to have one less than nsect
>for MSCP devices.

Assuming only one sector per track is unwise.  The `get unit status'
end packet includes information on the number of reserved sectors per
track.

>Some of the problems could have been solved with better info on
>MSCP. I have nothing on this. Is there anyone who can point me to
>some reliable documentation ?

No---or at least not yet....

(`Shipped on the tenth'... let me see... that means I should see
them by the end of the year....)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu