From: rp at servium.ch (Rico Pajarola)
Subject: [COFF] Disk Technology was [Simh] Which PDP-11 to choose
Date: Tue, 2 Jul 2019 14:34:21 -0700 [thread overview]
Message-ID: <CACwAiQn6b28MsTX1JwxPSFa5o7_7BKfcf83Nv9v4mABBueQ=bg@mail.gmail.com> (raw)
In-Reply-To: <CAC0cEp9TYLquL=6QSNgAqdtwym9VnyFK96-+EwYOnK3=f7Sbrg@mail.gmail.com>
if you still have that story, I'd love to hear it. A quick search didn't
turn up anything except that Super Eagles is a Nigerian football team.
On Tue, Jul 2, 2019 at 12:59 PM John P. Linderman <jpl.jpl at gmail.com> wrote:
> I don't have authoritative info on the cause, I'm just repeating what I
> heard. A highly viscous substance like glue would explain why it took so
> long to fail. In any event, it was nasty. Worked perfectly long enough to
> build confidence, then failed spectacularly. It was widespread. I entered a
> "Sysadmin Horror Story" contest at a USENIX (San Diego?), and won with a
> "short story" entry: *Supereagles*. I still have the shark's tooth trophy.
>
> On Tue, Jul 2, 2019 at 9:41 AM Tim Wilkinson <tjw at twsoft.co.uk> wrote:
>
>>
>>
>> Interesting that it was the platter bonding. The explanation SI gave us
>> (They sold us the super Eagles along with their controller) was that it was
>> a lubricant. So I had assumed a bearing seal fail.
>>
>>
>>
>> Anyway after about 4 swap outs and a lot of lifting they lasted a further
>> 15 years until we knocked down the office with the original 750 and its big
>> brother an 8810 still in the computer room as all the resellers wanted
>> certificates of continuing maintenance that would have cost more than they
>> were willing to pay for those vaxs.
>>
>>
>>
>> *From:* John P. Linderman [mailto:jpl.jpl at gmail.com]
>> *Sent:* 02 July 2019 12:47
>> *To:* Larry McVoy <lm at mcvoy.com>
>> *Cc:* Clem Cole <clemc at ccc.com>; Patrick Finnegan <
>> pat at computer-refuge.org>; COFF <coff at minnie.tuhs.org>; Tim Wilkinson <
>> tjw at twsoft.co.uk>
>> *Subject:* Re: [COFF] Disk Technology was [Simh] Which PDP-11 to choose
>>
>>
>>
>> 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
>>
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>> <#m_-5102461650516400670_m_-7814325232288781299_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
> _______________________________________________
> 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/ad6ebbf1/attachment.html>
next prev parent reply other threads:[~2019-07-02 21:34 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
2019-07-02 13:41 ` tjw
2019-07-02 19:58 ` jpl.jpl
2019-07-02 21:34 ` rp [this message]
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='CACwAiQn6b28MsTX1JwxPSFa5o7_7BKfcf83Nv9v4mABBueQ=bg@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).