On Tue, 31 Mar 2009 15:54:09 -0500, Eric Bielefeld wrote:

>You may be right, but from your reply you apparently don't know for sure
>whether bad blocksizes actually take up more dasd or not.  Does anyone know
>whether this affects the total amount of dasd or not that can be used?

When I worked at Wayne State University in Detroit, we bought an RVA.  That
was IBM's re-branded Iceberg.  AFAIK, Sun also sells it as the SVA.  On that
box, all data stored on disk was compressed.  Because any new data written
to a track may not fit in the same location, every time data on a track was
written, the track was written to a new location, and only the disk space
required for the compressed data was used.

There was a special utility used to report on how much of the back-end disk
storage was used.  IIRC, it was called Net Capacity Load.  Allocating
another volume or creating a snapshot did not increase the NCL.

The micorcode has garbage collection routines that accumulate track areas
that are no longer used and background tasks that move data around in order
to maintain a contiguous area where new tracks can be written.  It is a
marvelous feat of engineering.  And it is no wonder that the Iceberg was so
much later getting to markket than originally planned.

In order for any DASD subsystem to be insensitive to blocksize, it would
have to do something similar, compressing out the gaps and storing the track
in discontiguous locations.

AFAIK, the rest of modern DASD subsystems allocate specific locations for
each logical volume, and therefore for each logical track.  There has to be
sufficient disk space to store the maximum amount of data in each track
location.  If short blocks are written, less data will fit in that logical
track.

I suppose you might ask why the disk can't store more short blocks on the
track, reducing (or eliminating) the inter-record gap.  But then, it
wouldn't behave like a 3390, would it?  What might that break?

-- 
Tom Marchant

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to