xref: /netbsd-src/share/man/man4/man4.vax/up.4 (revision b1c86f5f087524e68db12794ee9c3e3da1ab17a0)
1.\"	$NetBSD: up.4,v 1.16 2009/04/11 22:20:07 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 June 5, 1993
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.Pp
108.Bl -hang
109.It Tn CDC No 9762 partitions
110.Bl -column diskx undefined length "xxx-yyyy" -compact
111.It Sy disk	start	length	cyls
112.It hp?a	0	15884	0-99
113.It hp?b	16000	33440	100-309
114.It hp?c	0	131680	0-822
115.It hp?d	49600	15884	309-408
116.It hp?e	65440	55936	409-758
117.It hp?f	121440	10080	759-822
118.It hp?g	49600	82080	309-822
119.El
120.It Tn CDC No 9766 300M drive partitions
121.Bl -column diskx undefined length "xxx-yyyy" -compact
122.It Sy disk	start	length	cyl
123.It up?a	0	15884	0-26
124.It up?b	16416	33440	27-81
125.It up?c	0	500384	0-822
126.It up?d	341696	15884	562-588
127.It up?e	358112	55936	589-680
128.It up?f	414048	861760	681-822
129.It up?g	341696	158528	562-822
130.It up?h	49856	291346	82-561
131.El
132.It Tn AMPEX DM Ns No 980 partitions
133.Bl -column diskx undefined length "xxx-yyyy" -compact
134.It Sy disk	start	length	cyls
135.It hp?a	0	15884	0-99
136.It hp?b	16000	33440	100-309
137.It hp?c	0	131680	0-822
138.It hp?d	49600	15884	309-408
139.It hp?e	65440	55936	409-758
140.It hp?f	121440	10080	759-822
141.It hp?g	49600	82080	309-822
142.El
143.It Tn AMPEX No 9300 300M drive partitions
144.Bl -column diskx undefined length "xxx-yyyy" -compact
145.It Sy disk	start	length	cyl
146.It up?a	0	15884	0-26
147.It up?b	16416	33440	27-81
148.It up?c	0	495520	0-814
149.It up?d	341696	15884	562-588
150.It up?e	358112	55936	589-680
151.It up?f	414048	81312	681-814
152.It up?g	341696	153664	562-814
153.It up?h	49856	291346	82-561
154.El
155.It Tn AMPEX No Capricorn 330M drive partitions
156.Bl -column diskx undefined length "xxx-yyyy" -compact
157.It Sy disk	start	length	cyl
158.It hp?a	0	15884	0-31
159.It hp?b	16384	33440	32-97
160.It hp?c	0	524288	0-1023
161.It hp?d	342016	15884	668-699
162.It hp?e	358400	55936	700-809
163.It hp?f	414720	109408	810-1023
164.It hp?g	342016	182112	668-1023
165.It hp?h	50176	291346	98-667
166.El
167.It Tn FUJITSU No 160M drive partitions
168.Bl -column diskx undefined length "xxx-yyyy" -compact
169.It Sy disk	start	length	cyl
170.It up?a	0	15884	0-49
171.It up?b	16000	33440	50-154
172.It up?c	0	263360	0-822
173.It up?d	49600	15884	155-204
174.It up?e	65600	55936	205-379
175.It up?f	121600	141600	380-822
176.It up?g	49600	213600	155-822
177.El
178.It Tn FUJITSU No Eagle partitions
179.Bl -column diskx undefined length "xxx-yyyy" -compact
180.It Sy disk	start	length	cyls
181.It hp?a	0	15884	0-16
182.It hp?b	16320	66880	17-86
183.It hp?c	0	808320	0-841
184.It hp?d	375360	15884	391-407
185.It hp?e	391680	55936	408-727
186.It hp?f	698880	109248	728-841
187.It hp?g	375360	432768	391-841
188.It hp?h	83520	291346	87-390
189.El
190.El
191.Pp
192The up?a partition is normally used for the root file system,
193the up?b partition as a paging area,
194and the up?c partition for pack-pack copying (it maps the entire disk).
195On 160M drives the up?g partition maps the rest of the pack.
196On other drives both up?g and up?h are used to map the
197remaining cylinders.
198.Sh FILES
199.Bl -tag -width Pa -compact
200.It Pa /dev/up[0-7][a-h]
201block files
202.It Pa /dev/rup[0-7][a-h]
203raw files
204.El
205.Sh DIAGNOSTICS
206.Bl -diag
207.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b."
208An unrecoverable error occurred during transfer of the specified
209filesystem block number(s),
210which are logical block numbers on the indicated partition.
211The contents of the cs2, er1 and er2 registers are printed
212in octal and symbolically with bits decoded.
213The error was either unrecoverable, or a large number of retry attempts
214(including offset positioning and drive recalibration) could not
215recover the error.
216.Pp
217.It "up%d: write locked."
218The write protect switch was set on the drive
219when a write was attempted.
220The write operation is not recoverable.
221.Pp
222.It "up%d: not ready."
223The drive was spun down or off line when it was
224accessed.
225The I/O operation is not recoverable.
226.Pp
227.It "up%d: not ready (flakey)."
228The drive was not ready, but after
229printing the message about being not ready (which takes a fraction
230of a second) was ready.
231The operation is recovered if no further errors occur.
232.Pp
233.It "up%d%c: soft ecc reading fsbn %d[-%d]."
234A recoverable ECC error occurred on the
235specified sector of the specified disk partition.
236This happens normally
237a few times a week.
238If it happens more frequently than this the sectors where the errors
239are occurring should be checked to see if certain cylinders on the
240pack, spots on the carriage of the drive or heads are indicated.
241.Pp
242.It "sc%d: lost interrupt."
243A timer watching the controller detecting
244no interrupt for an extended period while an operation was outstanding.
245This indicates a hardware or software failure.
246There is currently a hardware/software problem with spinning down
247drives while they are being accessed which causes this error to
248occur.
249The error causes a
250.Tn UNIBUS
251reset, and retry of the pending operations.
252If the controller continues to lose interrupts, this error will recur
253a few seconds later.
254.El
255.Sh SEE ALSO
256.Xr hk 4 ,
257.Xr hp 4 ,
258.Xr uda 4
259.Sh HISTORY
260The
261.Nm up
262driver appeared in
263.Bx 4.0 .
264.Sh BUGS
265A program to analyze the logged error information (even in its
266present reduced form) is needed.
267.Pp
268The partition tables for the file systems should be read off of each
269pack, as they are never quite what any single installation would prefer,
270and this would make packs more portable.
271