xref: /netbsd/share/man/man4/man4.vax/ut.4 (revision bf9ec67e)
1.\"	$NetBSD: ut.4,v 1.8 2001/08/18 14:37:49 wiz Exp $
2.\"
3.\" Copyright (c) 1983, 1991, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by the University of
17.\"	California, Berkeley and its contributors.
18.\" 4. Neither the name of the University nor the names of its contributors
19.\"    may be used to endorse or promote products derived from this software
20.\"    without specific prior written permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32.\" SUCH DAMAGE.
33.\"
34.\"     from: @(#)ut.4	8.1 (Berkeley) 6/5/93
35.\"
36.Dd June 5, 1993
37.Dt UT 4 vax
38.Os
39.Sh NAME
40.Nm ut
41.Nd
42.Tn UNIBUS TU45
43tri-density tape drive interface
44.Sh SYNOPSIS
45.Cd "ut0 at uba0 csr 0172440 vector utintr"
46.Cd "tj0 at ut0 drive 0"
47.Sh DESCRIPTION
48NOTE: This driver has not been ported from
49.Bx 4.4
50yet.
51.Pp
52The
53.Nm ut
54interface provides access to a standard tape drive interface as
55describe in
56.Xr mtio 4 .
57Hardware implementing this on the
58.Tn VAX
59is typified by the System
60Industries
61.Tn SI
629700 tape subsystem.  Tapes may be read or written
63at 800, 1600, and 6250
64.Tn BPI .
65.Sh DIAGNOSTICS
66.Bl -diag
67.It tj%d: no write ring.
68An attempt was made to write on the tape drive
69when no write ring was present; this message is written on the terminal of
70the user who tried to access the tape.
71.Pp
72.It tj%d: not online.
73An attempt was made to access the tape while it
74was offline; this message is written on the terminal of the user
75who tried to access the tape.
76.Pp
77.It tj%d: can't change density in mid-tape.
78An attempt was made to write
79on a tape at a different density than is already recorded on the tape.
80This message is written on the terminal of the user who tried to switch
81the density.
82.Pp
83.It "ut%d: soft error bn%d cs1=%b er=%b cs2=%b ds=%b."
84The formatter indicated a corrected error at a density other
85than 800bpi.  The data transferred is assumed to be correct.
86.Pp
87.It "ut%d: hard error bn%d cs1=%b er=%b cs2=%b ds=%b."
88A tape error occurred
89at block
90.Pp
91.It bn.
92Any error is
93fatal on non-raw tape; when possible the driver will have retried
94the operation which failed several times before reporting the error.
95.Pp
96.It tj%d: lost interrupt.
97A tape operation did not complete
98within a reasonable time, most likely because the tape was taken
99off-line during rewind or lost vacuum.  The controller should, but does not,
100give an interrupt in these cases.  The device will be made available
101again after this message, but any current open reference to the device
102will return an error as the operation in progress aborts.
103.El
104.Sh SEE ALSO
105.Xr mt 1 ,
106.Xr mtio 4
107.Sh HISTORY
108The
109.Nm
110driver appeared in
111.Bx 4.2 .
112.Sh BUGS
113May hang if a physical error (non-data) occurs.
114