![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to vddc.4 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man4|
Return to vddc.4 CVS log | Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man4 |
1.1 root 1: .TH VDDC 4 "15 May 1984"
2: .UC 4
3: .SH NAME
4: fsd, smd, xfd, fuj, xsd \- versabus storage module controller/drives
5: .SH SYNOPSIS
6: .B "VDDC controller at vba address ff2000"
7: .br
8: .B "160 Mb FSD "
9: .br
10: .B "300 Mb SMD "
11: .br
12: .B "340 Mb XFD "
13: .br
14: .B "360 Mb FUJ "
15: .br
16: .B "340 Mb XSD "
17: .SH DESCRIPTION
18: This is a generic VERSABUS storage module disk driver for CCI's VDDC
19: controller.
20: .PP
21: Files with minor device numbers 0 through 7 refer to various portions
22: of drive 0;
23: minor devices 8 through 15 refer to drive 1, etc.
24: The standard device names begin with `fsd, `smd', `fuj', `xfd',
25: or `xfd' followed by
26: the drive number and then a letter a-h for partitions 0-7 respectively.
27: The character ? stands here for a drive number in the range 0-7.
28: .PP
29: The block files access the disk via the system's normal
30: buffering mechanism and may be read and written without regard to
31: physical disk records. There is also a `raw' interface
32: which provides for direct transmission between the disk
33: and the user's read or write buffer.
34: A single read or write call results in exactly one I/O operation
35: and therefore raw I/O is considerably more efficient when
36: many words are transmitted. The names of the raw files
37: conventionally begin with an extra `r.'
38: .PP
39: In raw I/O counts should be a multiple of 512 bytes (a disk sector).
40: Likewise
41: .I seek
42: calls should specify a multiple of 512 bytes.
43: .SH "DISK SUPPORT"
44: The driver tries to access the last track on each drive
45: to determine the type of drive attached. The driver recognizes
46: five different drives: CDC FSD (160 Mb), CDC 9766 (300 Mb),
47: CDC XFSD (340 Mb), CDC 515Mb, and Fujitsu 36 Mb.
48: The origin and size of the pseudo-disks on each drive are
49: as follows:
50: .PP
51: .nf
52: .ta .5i +\w'000000 'u +\w'000000 'u +\w'000000 'u
53: FSD 160Mb drive partitions:
54: disk start length cyl
55: fsd?a 0 9600 0 - 59
56: fsd?b 9600 12000 60 - 134
57: fsd?c 21600 109280 135 - 817
58: fsd?d 0 21600 0 - 134 (a & b)
59: fsd?e 0 130880 0 - 817 (whole disk)
60: fsd?f 9600 121280 60 - 817 (b & c)
61: fsd?g 21600 54720 135 - 476 (1st 1/2 of c)
62: fsd?h 76320 54560 477 - 817 (2nd 1/2 of c)
63: .PP
64: SMD (CDC 9766) 300Mb drive partitions:
65: disk start length cyl
66: smd?a 0 20064 0 - 65
67: smd?b 20064 13680 66 - 110
68: smd?c 33744 214928 111 - 817
69: smd?d 0 33744 0 - 110 (a & b)
70: smd?e 0 248672 0 - 817 (whole disk)
71: smd?f 20064 228608 66 - 817 (b & c)
72: smd?g 33744 107616 111 - 464 (1st 1/2 of c)
73: smd?h 141360 107312 465 - 817 (2nd 1/2 of c)
74: .PP
75: XFD 340Mb drive partitions:
76: disk start length cyl
77: xfd?a 0 20352 0 - 52
78: xfd?b 20352 20352 53 - 105
79: xfd?c 40704 230400 106 - 705
80: xfd?d 0 40704 0 - 105 (a & b)
81: xfd?e 0 271104 0 - 705 (whole disk)
82: xfd?f 20352 250752 53 - 705 (b & c)
83: xfd?g 40704 115200 106 - 464 (1st 1/2 of c)
84: xfd?h 155904 115200 406 - 705 (2nd 1/2 of c)
85: .PP
86: FUJ 360Mb drive partitions:
87: disk start length cyl
88: fuj?a 0 19200 0 - 59
89: fuj?b 19200 24000 60 - 134
90: fuj?c 43200 218560 135 - 817
91: fuj?d 0 43200 0 - 134 (a & b)
92: fuj?e 0 261760 0 - 817 (whole disk)
93: fuj?f 19200 242560 60 - 817 (b & c)
94: fuj?g 43200 109440 135 - 476 (1st 1/2 of c)
95: fuj?h 152640 109120 477 - 817 (2nd 1/2 of c)
96: .PP
97: XSD 515Mb drive partitions:
98: disk start length cyl
99: xsd?a 0 30528 0 - 52
100: xsd?b 30528 30528 53 - 105
101: xsd?c 61056 345600 106 - 705
102: xsd?d 0 61056 0 - 105 (a & b)
103: xsd?e 0 406656 0 - 705 (whole disk)
104: xsd?f 30528 376128 53 - 705 (b & c)
105: xsd?g 61056 172800 106 - 464 (1st 1/2 of c)
106: xsd?h 233856 172800 406 - 705 (2nd 1/2 of c)
107: .fi
108: .PP
109: It is unwise for all of these files to be present in one installation,
110: since there is overlap in addresses and protection becomes
111: a sticky matter.
112: The ?a partition is normally used for the root file system,
113: and the ?b partition as a paging area.
114: The ?c partition maps the rest of the pack,
115: except the last 5 cylinders which are reserved for bad sector forwarding,
116: and diagnostic use.
117: The ?e partition may be used for pack-pack copying
118: (they maps the entire disk without the last 5 cylinders).
119: .SH FILES
120: /dev/fsd[0-7][a-f] fsd block files
121: .br
122: /dev/rfsd[0-7][a-f] fsd raw files
123: .br
124: /dev/smd[0-7][a-f] smd block files
125: .br
126: /dev/rsmd[0-7][a-f] smd raw files
127: .br
128: /dev/xfd[0-7][a-f] xfd block files
129: .br
130: /dev/rxfd[0-7][a-f] xfd raw files
131: .br
132: /dev/fuj[0-7][a-f] fuj block files
133: .br
134: /dev/rfuj[0-7][a-f] fuj raw files
135: .br
136: /dev/xsd[0-7][a-f] xsd block files
137: .br
138: /dev/rxsd[0-7][a-f] xsd raw files
139: .br
140: .SH SEE ALSO
141: disktab(5)
142: .SH DIAGNOSTICS
143: The driver prints out a number of error messages, indicating that
144: the error bit in the DCB'c op error status register was set.
145: The contents of the register are printed, as well as an indication
146: of the operation attempted and drive number.
147: .SH BUGS
148: In raw I/O
149: .I read
150: and
151: .IR write (2)
152: truncate file offsets to 1024-byte block boundaries,
153: and
154: .I write
155: scribbles on the tail of incomplete blocks.
156: Thus,
157: in programs that are likely to access raw devices,
158: .I read, write
159: and
160: .IR lseek (2)
161: should always deal in 1024-byte multiples.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.