Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ mtio(4) — SunOS 1.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

mt(1)

tar(1)

ar(4S)

tm(4S)

MTIO(4)  —  System Manager’s Manual — Special Files

NAME

mtio − UNIX magnetic tape interface

DESCRIPTION

The files mt0, ..., mt15 refer to the UNIX magtape drives, which read and write magnetic tape in 2048 byte blocks.  (The 2048 is actually BLKDEV_IOSIZE in <sys/param.h>.)  The following description applies to any of the transport/controller pairs.  The files mt0, ..., mt3 and mt8, ..., mt11 are rewound when closed; the others are not.  When a file open for writing is closed, two end-of-files are written.  If the tape is not to be rewound it is positioned with the head between the two tapemarks. 

The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files.  When foreign tapes are to be dealt with, and especially when long records are to be read or written, the ‘raw’ interface is appropriate.  The associated files are named rmt0, ..., rmt15, but the same minor-device considerations as for the regular files still apply.  A number of other ioctl operations are available on raw magnetic tape.  The following definitions are from <sys/mtio.h>:

/∗
 ∗ Structures and definitions for mag tape io control commands
 ∗/
 /∗ structure for MTIOCTOP - mag tape op command ∗/
structmtop{
shortmt_op;/∗ operations defined below ∗/
daddr_tmt_count;/∗ how many of them ∗/
};
 /∗ operations ∗/
#define MTWEOF0/∗ write an end-of-file record ∗/
#define MTFSF1/∗ forward space file ∗/
#define MTBSF2/∗ backward space file ∗/
#define MTFSR3/∗ forward space record ∗/
#define MTBSR4/∗ backward space record ∗/
#define MTREW5/∗ rewind ∗/
#define MTOFFL6/∗ rewind and put the drive offline ∗/
#define MTNOP7/∗ no operation, sets status only ∗/
 /∗ structure for MTIOCGET - mag tape get status command ∗/
 structmtget{
shortmt_type;/∗ type of magtape device ∗/
/∗ the following two registers are grossly device dependent ∗/
shortmt_dsreg;/∗ “drive status” register ∗/
shortmt_erreg;/∗ “error” register ∗/
/∗ end device-dependent registers ∗/
shortmt_resid;/∗ residual count ∗/
/∗ the following two are not yet implemented ∗/
daddr_tmt_fileno;/∗ file number of current position ∗/
daddr_tmt_blkno;/∗ block number of current position ∗/
/∗ end not yet implemented ∗/
};
 /∗
 ∗ Constants for mt_type byte
 ∗/
#defineMT_ISTS0x01/∗ vax: unibus ts-11 ∗/
#defineMT_ISHT0x02/∗ vax: massbus tu77, etc ∗/
#defineMT_ISTM0x03/∗ vax: unibus tm-11 ∗/
#defineMT_ISMT0x04/∗ vax: massbus tu78 ∗/
#defineMT_ISUT0x05/∗ vax: unibus gcr ∗/
#defineMT_ISCPC0x06/∗ sun: Multibus tapemaster ∗/
#defineMT_ISAR0x07/∗ sun: Multibus archive ∗/
 /∗ mag tape io control commands ∗/
#defineMTIOCTOP_IOW(m, 1, struct mtop)/∗ do a mag tape op ∗/
#defineMTIOCGET_IOR(m, 2, struct mtget)/∗ get tape status ∗/
 #ifndef KERNEL
#defineDEFTAPE"/dev/rmt12"
#endif

Each read or write call reads or writes the next record on the tape.  In the write case the record has the same length as the buffer given.  During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size.  In raw tape I/O seeks are ignored.  A zero byte count is returned when a tape mark is read, but another read will fetch the first record of the new tape file. 

FILES

/dev/mt? 
/dev/rmt?
/dev/rar?

SEE ALSO

mt(1), tar(1), ar(4S), tm(4S)

Sun System Release 1.0  —  17 August 1983

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026