xref: /netbsd-src/share/man/man4/man4.vax/up.4 (revision 721f013c3dccf382f4ff007505a6e4eeae891802)
1.\"	$NetBSD: up.4,v 1.19 2017/08/01 11:11:17 wiz Exp $
2.\"
3.\" Copyright (c) 1991, 1993, 19801988
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. Neither the name of the University nor the names of its contributors
15.\"    may be used to endorse or promote products derived from this software
16.\"    without specific prior written permission.
17.\"
18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28.\" SUCH DAMAGE.
29.\"
30.\"     from: @(#)up.4	8.1 (Berkeley) 6/5/93
31.\"
32.Dd February 17, 2017
33.Dt UP 4 vax
34.Os
35.Sh NAME
36.Nm up
37.Nd UNIBUS storage module controller/disk drives
38.Sh SYNOPSIS
39.Cd "sc0 at uba? csr 0176700 vector upintr"
40.Cd "up0 at sc0 drive 0"
41.Sh DESCRIPTION
42NOTE: This driver has not been ported from
43.Bx 4.4
44yet.
45.Pp
46This is a generic
47.Tn UNIBUS
48storage module disk driver.
49It is specifically designed to work with the
50Emulex
51.Tn SC-21
52and
53.Tn SC-31
54controllers.
55It can be easily
56adapted to other controllers (although bootstrapping will
57not necessarily be directly possible.)
58.Pp
59The script
60.Xr MAKEDEV 8
61should be used to create the
62.Nm up
63special files; consult
64.Xr mknod 8
65if a special file needs to be made manually.
66It is recommended as a security precaution to not create special files
67for devices which may never be installed.
68.Sh DISK SUPPORT
69The driver interrogates the controller's holding register
70to determine the type of drive attached.
71The driver recognizes seven different drives:
72.Tn CDC
739762,
74.Tn CDC
759766,
76.Tn AMPEX DM Ns 980 ,
77.Tn AMPEX
789300,
79.Tn AMPEX
80Capricorn,
81.Tn FUJITSU
82160, and
83.Tn FUJITSU
84Eagle
85(the Eagle is not supported by the SC-21).
86.Pp
87Special file names begin with
88.Sq Li up
89and
90.Sq Li rup
91for the block and character files respectively.
92The second component of the name, a drive unit number in the range
93of zero to seven, is represented by a
94.Sq Li \&?
95in the disk layouts below.
96The last component of the name, the file system partition, is
97designated by a letter from
98.Sq Li a
99to
100.Sq Li h
101which also corresponds to a minor device number set: zero to seven,
102eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
103three respectively (see
104.Xr physio 4 ) .
105The location and size (in 512 byte sectors) of the
106partitions for the above drives:
107.Bl -hang
108.It Tn CDC No 9762 partitions
109.Bl -column diskx undefined length "xxx-yyyy" -compact
110.It Sy disk	start	length	cyls
111.It hp?a	0	15884	0-99
112.It hp?b	16000	33440	100-309
113.It hp?c	0	131680	0-822
114.It hp?d	49600	15884	309-408
115.It hp?e	65440	55936	409-758
116.It hp?f	121440	10080	759-822
117.It hp?g	49600	82080	309-822
118.El
119.It Tn CDC No 9766 300M drive partitions
120.Bl -column diskx undefined length "xxx-yyyy" -compact
121.It Sy disk	start	length	cyl
122.It up?a	0	15884	0-26
123.It up?b	16416	33440	27-81
124.It up?c	0	500384	0-822
125.It up?d	341696	15884	562-588
126.It up?e	358112	55936	589-680
127.It up?f	414048	861760	681-822
128.It up?g	341696	158528	562-822
129.It up?h	49856	291346	82-561
130.El
131.It Tn AMPEX DM Ns No 980 partitions
132.Bl -column diskx undefined length "xxx-yyyy" -compact
133.It Sy disk	start	length	cyls
134.It hp?a	0	15884	0-99
135.It hp?b	16000	33440	100-309
136.It hp?c	0	131680	0-822
137.It hp?d	49600	15884	309-408
138.It hp?e	65440	55936	409-758
139.It hp?f	121440	10080	759-822
140.It hp?g	49600	82080	309-822
141.El
142.It Tn AMPEX No 9300 300M drive partitions
143.Bl -column diskx undefined length "xxx-yyyy" -compact
144.It Sy disk	start	length	cyl
145.It up?a	0	15884	0-26
146.It up?b	16416	33440	27-81
147.It up?c	0	495520	0-814
148.It up?d	341696	15884	562-588
149.It up?e	358112	55936	589-680
150.It up?f	414048	81312	681-814
151.It up?g	341696	153664	562-814
152.It up?h	49856	291346	82-561
153.El
154.It Tn AMPEX No Capricorn 330M drive partitions
155.Bl -column diskx undefined length "xxx-yyyy" -compact
156.It Sy disk	start	length	cyl
157.It hp?a	0	15884	0-31
158.It hp?b	16384	33440	32-97
159.It hp?c	0	524288	0-1023
160.It hp?d	342016	15884	668-699
161.It hp?e	358400	55936	700-809
162.It hp?f	414720	109408	810-1023
163.It hp?g	342016	182112	668-1023
164.It hp?h	50176	291346	98-667
165.El
166.It Tn FUJITSU No 160M drive partitions
167.Bl -column diskx undefined length "xxx-yyyy" -compact
168.It Sy disk	start	length	cyl
169.It up?a	0	15884	0-49
170.It up?b	16000	33440	50-154
171.It up?c	0	263360	0-822
172.It up?d	49600	15884	155-204
173.It up?e	65600	55936	205-379
174.It up?f	121600	141600	380-822
175.It up?g	49600	213600	155-822
176.El
177.It Tn FUJITSU No Eagle partitions
178.Bl -column diskx undefined length "xxx-yyyy" -compact
179.It Sy disk	start	length	cyls
180.It hp?a	0	15884	0-16
181.It hp?b	16320	66880	17-86
182.It hp?c	0	808320	0-841
183.It hp?d	375360	15884	391-407
184.It hp?e	391680	55936	408-727
185.It hp?f	698880	109248	728-841
186.It hp?g	375360	432768	391-841
187.It hp?h	83520	291346	87-390
188.El
189.El
190.Pp
191The up?a partition is normally used for the root file system,
192the up?b partition as a paging area,
193and the up?c partition for pack-pack copying (it maps the entire disk).
194On 160M drives the up?g partition maps the rest of the pack.
195On other drives both up?g and up?h are used to map the
196remaining cylinders.
197.Sh FILES
198.Bl -tag -width Pa -compact
199.It Pa /dev/up[0-7][a-h]
200block files
201.It Pa /dev/rup[0-7][a-h]
202raw files
203.El
204.Sh DIAGNOSTICS
205.Bl -diag
206.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b."
207An unrecoverable error occurred during transfer of the specified
208filesystem block number(s),
209which are logical block numbers on the indicated partition.
210The contents of the cs2, er1 and er2 registers are printed
211in octal and symbolically with bits decoded.
212The error was either unrecoverable, or a large number of retry attempts
213(including offset positioning and drive recalibration) could not
214recover the error.
215.It "up%d: write locked."
216The write protect switch was set on the drive
217when a write was attempted.
218The write operation is not recoverable.
219.It "up%d: not ready."
220The drive was spun down or off line when it was
221accessed.
222The I/O operation is not recoverable.
223.It "up%d: not ready (flakey)."
224The drive was not ready, but after
225printing the message about being not ready (which takes a fraction
226of a second) was ready.
227The operation is recovered if no further errors occur.
228.It "up%d%c: soft ecc reading fsbn %d[-%d]."
229A recoverable ECC error occurred on the
230specified sector of the specified disk partition.
231This happens normally
232a few times a week.
233If it happens more frequently than this the sectors where the errors
234are occurring should be checked to see if certain cylinders on the
235pack, spots on the carriage of the drive or heads are indicated.
236.It "sc%d: lost interrupt."
237A timer watching the controller detecting
238no interrupt for an extended period while an operation was outstanding.
239This indicates a hardware or software failure.
240There is currently a hardware/software problem with spinning down
241drives while they are being accessed which causes this error to
242occur.
243The error causes a
244.Tn UNIBUS
245reset, and retry of the pending operations.
246If the controller continues to lose interrupts, this error will recur
247a few seconds later.
248.El
249.Sh SEE ALSO
250.Xr vax/hk 4 ,
251.Xr vax/hp 4 ,
252.Xr vax/uda 4
253.Sh HISTORY
254The
255.Nm up
256driver appeared in
257.Bx 4.0 .
258.Sh BUGS
259A program to analyze the logged error information (even in its
260present reduced form) is needed.
261.Pp
262The partition tables for the file systems should be read off of each
263pack, as they are never quite what any single installation would prefer,
264and this would make packs more portable.
265