Hi Gurus,
Thanks to
Alan
Ken Kleiner
Colin Walters
Dr Tom Blinn
James Sainsbury
Michael Polnick
Irvine Short
In fact the system has created several tape drivers in /dev/tape
and /dev/ntape during installation, like tape0_d* and tape0c, aside
tape0. They have a certain variety of densities and this can be
checked in the manual pages for "tz". There is there even an
equivalence table with respect to the old drivers:
________________________________________________________________________
Previous Format in /dev New Formats in /dev/nrmt and /dev/rmt
________________________________________________________________________
rmt?a tape?_d3
rmt?l tape?_d0 (d0 always maps to the low density)
rmt?m tape?_d2
rmt?h tape?_d1 (d1 always maps to the high density)
________________________________________________________________________
As another reference, Michael sent the following:
/dev/ntape/tape0 is default density, no compression
/dev/ntape/tape0c is default density, with compression
/dev/ntape/tape0_d1 is highest density, with compression
Colin stresses that such informations are contained in the Chapter 5
of the Administration Guide.
So now I know how use my tape unit correctly. Other useful references
can be found in the pages for ddr_config (8) and ddr.dbase (4), in the
case the vendor is not DEC, which is not our situation.
Thanks again,
Oyanarte Portilho
Institute of Physics
University of Brasilia
-----Original post:
> We have upgraded from DU 4.0a to Tru64 v. 5.0a and before
> that our DAT tape unit could record up to 8 Gb in a 90
> meters tape (driver /dev/nrmt*h). Now the only driver created
> by the system during installation is /dev/ntape/tape0,
> which provides a low density recording of 2 Gb in the same
> tape. How to recover higher density drivers in True64 Unix
> v. 5.0a?
Received on Tue Oct 17 2000 - 13:26:45 NZDT