On Wed, 12 Aug 2015 13:21:45 -0500, Joel Ewing wrote:
My strong impression was that the erased IBG between physical blocks was a
requirement for proper sensing of beginning of a block. The requirement
that some 32-byte increments must be left unused for IBGs indicates
these 32-byte groupings
inudstry move to 4096-byte
fixed blocks for improved error correction and track capacity.
https://en.wikipedia.org/wiki/Advanced_Format
http://www.seagate.com/tech-insights/advanced-format-4k-sector-hard-drives-master-ti/
re:
http://www.garlic.com/~lynn/2015g.html#4 3380 was actually FBA
In another thread, l...@garlic.com wrote:
... but then if MVS had FBA support wouldn't have needed to do 3380 as CKD
(even tho inherently it was FBA underneath) ...
I didn't know that.
Was that the first (and/or last?) IBM SLED to be inherently FBA under the hood?
Where were the smarts for
The important distinction of FBA is that block headers aren't rewritten when
the data is changed.
(Not counting when a low-level format is done, normally for the whole drive.)
I don't know the low-level details of the 3380 to know. It might be that the
32 byte
blocks are related to ECC, and
jcal...@narsil.org (Jerry Callen) writes:
In another thread, l...@garlic.com wrote:
... but then if MVS had FBA support wouldn't have needed to do 3380
as CKD (even tho inherently it was FBA underneath) ...
I didn't know that.
Was that the first (and/or last?) IBM SLED to be inherently
On 08/12/2015 07:38 AM, Jerry Callen wrote:
In another thread, l...@garlic.com wrote:
... but then if MVS had FBA support wouldn't have needed to do 3380 as CKD
(even tho inherently it was FBA underneath) ...
I didn't know that.
Was that the first (and/or last?) IBM SLED to be
