![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to hk.4 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / vax|
Return to hk.4 CVS log | Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / vax |
1.1 root 1: .\" Copyright (c) 1980 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)hk.4 6.3 (Berkeley) 6/13/88
6: .\"
7: .TH HK 4 "June 13, 1988"
8: .UC 4
9: .SH NAME
10: hk \- RK6-11/RK06 and RK07 moving head disk
11: .SH SYNOPSIS
12: .B "controller hk0 at uba? csr 0177440 vector rkintr"
13: .br
14: .B "disk rk0 at hk0 drive 0"
15: .SH DESCRIPTION
16: Files with minor device numbers 0 through 7 refer to various portions
17: of drive 0;
18: minor devices 8 through 15 refer to drive 1, etc.
19: The standard device names begin with ``hk'' followed by
20: the drive number and then a letter a-h for partitions 0-7 respectively.
21: The character ? stands here for a drive number in the range 0-7.
22: .PP
23: The block files access the disk via the system's normal
24: buffering mechanism and may be read and written without regard to
25: physical disk records. There is also a `raw' interface
26: which provides for direct transmission between the disk
27: and the user's read or write buffer.
28: A single read or write call results in exactly one I/O operation
29: and therefore raw I/O is considerably more efficient when
30: many words are transmitted. The names of the raw files
31: conventionally begin with an extra `r.'
32: .PP
33: In raw I/O counts should be a multiple of 512 bytes (a disk sector).
34: Likewise
35: .I seek
36: calls should specify a multiple of 512 bytes.
37: .SH "DISK SUPPORT"
38: The origin and size (in sectors) of the
39: pseudo-disks on each drive are as follows:
40: .PP
41: .nf
42: .ta .5i +\w'000000 'u +\w'000000 'u +\w'000000 'u
43: RK07 partitions:
44: disk start length cyl
45: hk?a 0 15884 0-240
46: hk?b 15906 10032 241-392
47: hk?c 0 53790 0-814
48: hk?d 25938 15884 393-633
49: hk?f 41844 11792 634-814
50: hk?g 25938 27786 393-813
51: .PP
52: RK06 partitions
53: disk start length cyl
54: hk?a 0 15884 0-240
55: hk?b 15906 11154 241-409
56: hk?c 0 27126 0-410
57: .DT
58: .fi
59: .PP
60: On a dual RK-07 system
61: partition hk?a is used
62: for the root for one drive
63: and partition hk?g for the /usr file system.
64: If large jobs are to be run using
65: hk?b on both drives as swap area provides a 10Mbyte paging area.
66: Otherwise
67: partition hk?c on the other drive
68: is used as a single large file system.
69: .SH FILES
70: /dev/hk[0-7][a-h] block files
71: .br
72: /dev/rhk[0-7][a-h] raw files
73: .SH SEE ALSO
74: hp(4),
75: uda(4),
76: up(4),
77: syslogd(8)
78: .SH DIAGNOSTICS
79: \fBhk%d%c: hard error %sing fsbn %d[-%d] cs2=%b ds=%b er=%b\fR.
80: An unrecoverable error occurred during transfer of the specified
81: filesystem block number(s),
82: which are logical block numbers on the indicated partition.
83: The contents of the cs2, ds and er registers are printed
84: in octal and symbolically with bits decoded.
85: The error was either unrecoverable, or a large number of retry attempts
86: (including offset positioning and drive recalibration) could not
87: recover the error.
88: .PP
89: \fBrk%d: write locked\fR. The write protect switch was set on the drive
90: when a write was attempted. The write operation is not recoverable.
91: .PP
92: \fBrk%d: not ready\fR. The drive was spun down or off line when it was
93: accessed. The i/o operation is not recoverable.
94: .PP
95: \fBrk%d: not ready (came back!)\fR. The drive was not ready, but after
96: printing the message about being not ready (which takes a fraction
97: of a second) was ready. The operation is recovered if no further
98: errors occur.
99: .PP
100: \fBup%d%c: soft ecc reading fsbn %d[-%d]\fP.
101: A recoverable ECC error occurred on the
102: specified sector(s) in the specified disk partition.
103: This happens normally
104: a few times a week. If it happens more frequently than
105: this the sectors where the errors are occurring should be checked to see
106: if certain cylinders on the pack, spots on the carriage of the drive
107: or heads are indicated.
108: .PP
109: \fBhk%d: lost interrupt\fR. A timer watching the controller detected
110: no interrupt for an extended period while an operation was outstanding.
111: This indicates a hardware or software failure. There is currently a
112: hardware/software problem with spinning down drives while they are
113: being accessed which causes this error to occur.
114: The error causes a UNIBUS reset, and retry of the pending operations.
115: If the controller continues to lose interrupts, this error will recur
116: a few seconds later.
117: .SH BUGS
118: In raw I/O
119: .I read
120: and
121: .IR write (2)
122: truncate file offsets to 512-byte block boundaries,
123: and
124: .I write
125: scribbles on the tail of incomplete blocks.
126: Thus,
127: in programs that are likely to access raw devices,
128: .I read, write
129: and
130: .IR lseek (2)
131: should always deal in 512-byte multiples.
132: .PP
133: DEC-standard error logging should be supported.
134: .PP
135: A program to analyze the logged error information (even in its
136: present reduced form) is needed.
137: .PP
138: The partition tables for the file systems should be read off of each
139: pack, as they are never quite what any single installation would prefer,
140: and this would make packs more portable.
141: .PP
142: The rk07 g partition size in rk.c disagrees with that in /etc/disktab.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.