Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Disk Technology was [Simh] Which PDP-11 to choose
Date: Tue, 2 Jul 2019 09:13:22 -0400	[thread overview]
Message-ID: <CAC20D2P=XxhGQpNy0tb-5=dWz-R16Dkb1+=9figy1onRMNHqHw@mail.gmail.com> (raw)
In-Reply-To: <CAC0cEp87V3OsNJteCHzQXD0x7hDerwmDrTqJ+P9jhXXjORjXYw@mail.gmail.com>

Yeah - although we discovered that the better the controller microcode was
at handling errors, the better life was for the user, disk vendor, and
system manufacturer.   On the VAX, the SI controller was not extremely
forgiving and I had left that world. I wonder if some of the super eagle's
issues were that the controller did not gracefully handle drive errors.
IIRC Emulex's SMI and Unibus controllers tended to be smarter than SI's.
 FWIW: Once Xylogic did the 45x series for the Multibus/later VME with *the
microcode solid* and Unix drivers got written to handle the errors
returned, my experiences were ( as Larry said ) we had few problems with
any of the SMD disks, even the Ampex, at either Masscomp or Stellar.

Truth is by then we had started to concentrate on ESDI 5.25" FF disks from
the 19" and 8" SMD technologies (using a cheap SCSI to ESDI controller).
But it was a little of "you get what you pay for" problem.   The new
controllers for the smaller disks cost a lot less  (Xylogic VME/Multibus
*vs.* SMS SCSI); so we were starting over with the SMS folks to educate
them.  Apollo had been SMS's primary partner (did you ever wonder why they
supported at 1056 byte block as one of their native block sizes), but to
the SMS's folks credit they picked up the ideas of good error recovery
reasonable fast.

Clem

PS The thing I fear lost to history was PC's code for the Masscomp
formatter/tester/exerciser for the 45x Series. It was an amazing piece of
work.  I think we still have the OS sources kicking around, but the
diagnostic system was of less interest I fear.

On Tue, Jul 2, 2019 at 7:47 AM John P. Linderman <jpl.jpl at gmail.com> wrote:

> There were eagles, and then there were super-eagles. Our experience with
> eagles was great, and we were eager to try the (larger) super-eagles. We
> soaked them for a month or so, then put them into production use.
> Whereupon, they started dropping like flies. It turns out the glue they
> used to attach the platters to the spindle slowly crept out over time,
> eventually coming to grief with a read/write head. This experience was
> wide-spread, and seriously damaged Fujitsu's reputation.
>
> On Mon, Jul 1, 2019 at 10:11 AM Larry McVoy <lm at mcvoy.com> wrote:
>
>> On Mon, Jul 01, 2019 at 09:49:42AM -0400, Clem Cole wrote:
>> >  An Eagle or Eagle-II was a whole lot lighter (and physically smaller)
>> than
>> > an RP06 or RP07 (or an RM series drive for that matter). It is
>> interesting
>> > to hear you had problems with the Eagles.   They were generally
>> considered
>> > the best/most reliable of the day.   The SI controller on the Vax was
>> less
>> > so, although many of us in the UNIX community used them.
>>
>> We ran Eagles on the Masscomps we had at Geophysics.  Nothing but good
>> things to say about those drives.
>> _______________________________________________
>> COFF mailing list
>> COFF at minnie.tuhs.org
>> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20190702/abc1565c/attachment.html>


  reply	other threads:[~2019-07-02 13:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6e8cdcbf-7183-1082-0437-403a6f3b2994@gmail.com>
     [not found] ` <25855953-9505-481C-A0E2-1AAD53B7BEC5@ccc.com>
     [not found]   ` <CAFrGgTSM9x7u6qxT9LFmG85UH_5u=-WivKDfQKkhK6LprNxmKg@mail.gmail.com>
     [not found]     ` <28FA3347-B880-400A-B606-1240C83FA867@ccc.com>
     [not found]       ` <CAADZ-4PtRYOF_S2shO86E2jb-xg_dOuknRxaGB0ZVeErNSZgCg@mail.gmail.com>
     [not found]         ` <CAC20D2M3y46c=xVPOxxzO4mwGWSJ_Bd3HrEUP3AtOAcr_0LvDA@mail.gmail.com>
     [not found]           ` <005401d5300f$74588a60$5d099f20$@twsoft.co.uk>
2019-07-01 13:49             ` clemc
2019-07-01 14:11               ` lm
2019-07-02 11:47                 ` jpl.jpl
2019-07-02 13:13                   ` clemc [this message]
2019-07-02 13:41                   ` tjw
2019-07-02 19:58                     ` jpl.jpl
2019-07-02 21:34                       ` rp
2019-07-03 18:02                         ` jpl.jpl
2019-07-03 18:38                           ` clemc
2019-07-03 18:42                             ` clemc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC20D2P=XxhGQpNy0tb-5=dWz-R16Dkb1+=9figy1onRMNHqHw@mail.gmail.com' \
    --to=coff@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).