Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tm(4) [bsd man page]

TM(4)							     Kernel Interfaces Manual							     TM(4)

NAME
tm - TM-11/TE-10 magtape interface SYNOPSIS
/sys/conf/SYSTEM: # Setting AVIVTM configures the TM driver for the AVIV 800/1600/6250 # controller. For more details, see /sys/pdpuba/tm.c. NTM tm_drives # TM11 AVIVTM YES # AVIV 800/1600/6250 controller /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments tm ? 172520 224 5 tmintr # tm11 driver major device number(s): raw: 7 block: 1 minor device encoding: bits 0003 specify TS drive bit 0004 specifies no-rewind operation bits 0030 specify recording density: 0000: 800BPI 0010: 1600BPI (AVIVTM and some other controllers) 0020: 6250BPI (AVIVTM only) DESCRIPTION
The tm-11/te-10 combination provides a standard tape drive interface as described in mtio(4). The standard DEC tm-11 operates only at 800 bpi. Other controllers of this type may also allow operation at 1600 bpi, under software control or by switching manually. FILES
/dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
mt(1), tar(1), tp(1), mtio(4), ht(4), ts(4), mt(4), dtab(5), autoconfig(8) DIAGNOSTICS
te%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi- nal of the user who tried to access the tape. te%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who tried to access the tape. te%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the tape. This message is written on the terminal of the user who tried to switch the density. te%d: hard error bn%d er=%b. A tape error occurred at block bn; the tm error register is printed in octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation which failed several times before reporting the error. te%d: lost interrupt. A tape operation did not complete within a reasonable time, most likely because the tape was taken off-line during rewind or lost vacuum. The controller should, but does not, give an interrupt in these cases. The device will be made available again after this message, but any current open reference to the device will return an error as the operation in progress aborts. BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed. 3rd Berkeley Distribution January 28, 1988 TM(4)

Check Out this Related Man Page

tz(4)							     Kernel Interfaces Manual							     tz(4)

Name
       tz - SCSI magnetic tape interface

Syntax
       VAX NCR 5380:
	 adapter      uba0    at nexus?
	 controller   scsi0   at uba0	 csr 0x200c0080  vector szintr
	 tape	      tz0     at scsi0	 drive 0

       VAX DEC SII:
	 adapter      ibus0   at nexus?
	 controller   sii0    at ibus?	 vector sii_intr
	 tape	      tz0     at sii0	 drive 0

       RISC DEC SII:
	 adapter      ibus0   at nexus?
	 controller   sii0    at ibus?	 vector sii_intr
	 tape	      tz0     at sii0	 drive 0

       RISC DEC KZQ:
	 adapter      uba0    at nexus?
	 controller   kzq0    at ibus? csr 0761300vector sii_intr
	 tape	      tz0     at kzq0	 drive 0

       RISC NCR ASC:
	 adapter      ibus0   at nexus?
	 controller   asc0    at ibus?	 vector ascintr
	 tape	      tz0     at asc0	 drive 0

Description
       The SCSI tape driver provides a standard tape drive interface as described in This is a driver for any Digital SCSI tape device.

       For  the  TZK10	QIC  format tape drive, the densities supported are QIC-24 (read only) block size of 512 byte blocks, QIC-120, and QIC-150
       read/write block size of 512 byte blocks, and QIC-320 read/write block size of 1024 byte blocks.  With QIC format style tapes all reads and
       writes  must  be  in  multiple  of the block size.  This is a requirement of fixed block tape drives because record boundaries are not pre-
       served.	The QIC densities are selected using the following special device names:

	 QIC-24 Fixed block size.
	 QIC-120 Fixed block size.
	 QIC-150 Fixed block size.
	 QIC-320 Fixed block size.

       With all fixed block tape devices a of a file to the tape must be padded out.  An example of this is a of which has a size of approximately
       3800 bytes.
       dd if=/etc/gettytab of=/dev/rmt0h bs=10k conv=sync
	 or
       dd if=/etc/gettytab of=/dev/rmt0l bs=512 conv=sync
       The option of pads the output to block size.

       This  driver  also  supports  n-buffered  reads	and  writes  to the raw tape interface (used with streaming tape drives).  See for further
       details.

Tape Support
       TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10

Diagnostics
       All diagnostic messages are sent to the error logger subsystem.

Files
See Also
       mtio(4), nbuf(4), SCSI(4), MAKEDEV(8), uerf(8), tapex(8)
       Guide to the Error Logger

																	     tz(4)
Man Page

Featured Tech Videos