home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!sgigate!odin!sgihub!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: why does an 6000 ft exabyte tape give 2.3Gb capacity?
- Message-ID: <ublvg64@zuni.esd.sgi.com>
- Date: 2 Jan 93 01:01:20 GMT
- References: <C06Bpu.2IJ@ie.utoronto.ca>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 23
-
- In <C06Bpu.2IJ@ie.utoronto.ca> andy@ie.utoronto.ca (Andy Sun) writes:
- | I know I am missing something, but I don't know what it is and will
- | appreciate your help.
- |
- | I know for a fact (from the dump(8) man page) that a 2.3Gbyte 8mm
- | Exabyte tape has a length of 6,000 feet and a density of 54,000 bits/inch.
- | What I don't understand is WHY 6,000 feet with 54,000 bits/inch would give
- | 2.3Gbyte?
-
- An Exabyte tape is neither 6000 feet long, nor does it have a density
- of 54000 bpi. These are just phony numbers to fake out the bizarre
- way dump (in almost all implementations) calculates capacity. dump
- thinks it 'knows' how much of the tape is lost to interrecord
- gaps at various densities.
-
- Most Exabyte tapes are 112 meters long (for the 2.3 GB capacity
- on an 8200 drive). I forget just what the density is; it partly
- depends on whether you include the 'unused' tape between the
- diagonal stripes, or just the area actually written.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-