2.9BSD/usr/man/man4/rk.4

Compare this file to the similar file:
Show the results in this format:
.TH RK 4 
.UC
.SH NAME
rk  \-  RK-11/RK03, RK05 disk
.SH DESCRIPTION
.I Rk?
refers to an entire disk as a single sequentially-addressed
file.
Its 512-byte blocks are numbered 0 to 4871.
Minor device numbers are drive numbers on one controller.
.PP
The block files
access the disk via the system's normal
buffering mechanism
and may be read and written without regard to
physical disk records.
There is also a `raw' interface
which provides for direct transmission between the disk
and the user's read or write buffer.
A single read or write call results in exactly one I/O operation
and therefore raw I/O is considerably more efficient when
many words are transmitted.
The names of the raw files conventionally begin with an extra `r.'
.PP
In raw I/O the buffer must begin on a word boundary,
and counts should be a multiple of 512 bytes
(a disk block).
Likewise
.I lseek
calls should specify a multiple of 512 bytes.
.SH FILES
.ta 2i
/dev/rk[0-7]	block files
.br
/dev/rrk[0-7]	raw files
.SH "SEE ALSO"
dvhp(4), hk(4), hp(4), hs(4), ml(4), rf(4), rl(4), rm(4), rp(4), rx2(4), xp(4)
.SH DIAGNOSTICS
\fBrk%d: hard error bn %d er=%b ds=%b\fP.  An unrecoverable
error occured during transfer of the specified sector of the specified
disk partition.  The contents of the two error registers are also printed
in octal and symbolically with bits decoded.
The error was either unrecoverable, or a large number of retry attempts
could not recover the error.
.PP
\fBrk%d: write locked\fP.  The write protect switch was set on the drive
when a write was attempted.  The write operation is not recoverable.
.SH BUGS
In raw I/O
.I read
and
.IR write (2)
truncate file offsets to 512-byte block boundaries,
and
.I write
scribbles on the tail of incomplete blocks.
Thus,
in programs that are likely to access raw devices,
.I read, write
and
.IR lseek (2)
should always deal in 512-byte multiples.
.PP
DEC-standard error logging should be supported.
.PP
A program to analyze the logged error information (even in its
present reduced form) is needed.