The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: paul.winalski@gmail.com (Paul Winalski)
Subject: [TUHS] 3330s, 3340s, Winchesters... (was: /dev/drum)
Date: Wed, 25 Apr 2018 16:54:16 -0400	[thread overview]
Message-ID: <CABH=_VS2C73=9eCDeC7eihfSSuz68E-eWLFzG0T3tZAo2SzLHQ@mail.gmail.com> (raw)
In-Reply-To: <20180425005251.GL31055@eureka.lemis.com>

On 4/24/18, Greg 'groggy' Lehey <grog at lemis.com> wrote:
>
> Hmm.  The earliest 3330s had 100 MB per disk, considerably more than
> the 3340.  I had thought that the 3340 had fewer surfaces.  And the
> 3330s definitely only had one disk per unit, though they brought out
> an 8-drive cabinet with a whopping 2.4 GB (by the time I used them).

The 3340 indeed had fewer platters per unit than the 3330, and because
of that a lower disk capacity.  Both the 3330 and 3340 were CKD
format, not fixed-block, so the capacity depended on the record size.
Highest storage capacity was achieved with one record with a
zero-length key field covering the full track (called full-track
blocking).

According to the IBM Archives web page
(https://www-03.ibm.com/ibm/history/exhibits/storage/storage_3330.html),
the 3330 was code-named Merlin.  It could have from 2 to 16 spindles
per controller.  Originally each disk pack had a maximum capacity of
100 MB.  The 3330 model 11 used IBM 3336 disk packs that had double
the original capacity (up to 200 MB).

This IBM Archives web page
(https://www-03.ibm.com/ibm/history/exhibits/storage/storage_3340.html)
says that the 3340 was code-named Winchester.  This page reports, but
does not verify, the "30-30" Winchester rifle story.  The IBM 3348
Data Module, the disk pack equivalent for the 3340, was a sealed
module that contained the head assembly.  This reduced the hazards of
head misalignment and surface contamination.  Unlike later
sealed-module disks, the 3348s were removable media.  Modules with
maximum capacities of 35 MB or 70 MB were available.  There was also a
70 MB module with up to 0.5 MB accessible from fixed heads.

-Paul W.


  reply	other threads:[~2018-04-25 20:54 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 15:02 [TUHS] /dev/drum Tim Bradshaw
2018-04-20 15:58 ` Clem Cole
2018-04-20 16:00 ` David Collantes
2018-04-20 16:12   ` Dan Cross
2018-04-20 16:21     ` Clem Cole
2018-04-20 16:33     ` Warner Losh
2018-04-20 19:17       ` Ron Natalie
2018-04-20 20:23         ` Clem Cole
2018-04-20 22:10         ` Dave Horsfall
2018-04-22 17:01     ` Lars Brinkhoff
2018-04-22 17:37       ` Clem Cole
2018-04-22 19:14         ` Bakul Shah
2018-04-22 20:58         ` Mutiny
2018-04-22 22:37           ` Clem cole
2018-04-22 21:51         ` Dave Horsfall
2018-04-25  1:27           ` Dan Stromberg
2018-04-25 12:18             ` Ronald Natalie
2018-04-25 13:39               ` Tim Bradshaw
2018-04-25 14:02                 ` arnold
2018-04-25 14:59                   ` tfb
2018-04-25 14:33               ` Ian Zimmerman
2018-04-25 14:46                 ` Larry McVoy
2018-04-25 15:03                   ` ron minnich
2018-04-25 20:29               ` Paul Winalski
2018-04-25 20:45                 ` Larry McVoy
2018-04-25 21:14                   ` Lawrence Stewart
2018-04-25 21:30                     ` ron minnich
2018-04-25 23:01                 ` Bakul Shah
2018-04-23 16:42         ` Tim Bradshaw
2018-04-23 17:30           ` Ron Natalie
2018-04-23 17:51             ` Clem Cole
2018-04-23 18:30               ` Ron Natalie
2018-04-25 14:02                 ` Tom Ivar Helbekkmo
2018-04-25 14:38                   ` Clem Cole
2018-04-23 20:47               ` Grant Taylor
2018-04-23 21:06                 ` Clem Cole
2018-04-23 21:14                   ` Dan Mick
2018-04-23 21:27                     ` Clem Cole
2018-04-24  3:28                       ` [TUHS] 3330s, 3340s, Winchesters... (was: /dev/drum) Greg 'groggy' Lehey
2018-04-24 11:43                         ` Paul Winalski
2018-04-24 13:13                           ` Clem Cole
2018-04-25  0:52                             ` Greg 'groggy' Lehey
2018-04-25 20:54                               ` Paul Winalski [this message]
2018-04-23 22:07                 ` [TUHS] /dev/drum Tim Bradshaw
2018-04-23 22:15                   ` Warner Losh
2018-04-23 23:30                     ` Grant Taylor
2018-04-24  9:37                       ` Michael Kjörling
2018-04-24  9:57                         ` Dave Horsfall
2018-04-24 13:01                           ` Nemo
2018-04-24 13:03                         ` Arthur Krewat
2018-04-25  1:31                       ` [TUHS] Disk data layout (was: /dev/drum) Greg 'groggy' Lehey
2018-04-25  6:43                         ` Hellwig Geisse
2018-04-25 21:17                         ` Paul Winalski
2018-04-25 21:55                           ` Bakul Shah
2018-04-27 15:47                           ` Dave Horsfall
2018-04-27 18:16                             ` Paul Winalski
2018-04-27 18:37                               ` Clem Cole
2018-04-23 23:45                   ` [TUHS] /dev/drum Arthur Krewat
2018-04-24  8:05                     ` tfb
2018-04-24 12:06 [TUHS] 3330s, 3340s, Winchesters... (was: /dev/drum) Noel Chiappa
2018-04-25  0:47 ` Greg 'groggy' Lehey
2018-04-25 14:15   ` Steffen Nurpmeso
2018-04-27  5:15     ` Dave Horsfall
2018-04-27 13:13       ` Steffen Nurpmeso
2018-04-27 14:42       ` Ian Zimmerman
2018-04-28  8:05         ` Wesley Parish

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='CABH=_VS2C73=9eCDeC7eihfSSuz68E-eWLFzG0T3tZAo2SzLHQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    /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).