summaryrefslogtreecommitdiffstats
path: root/man4/st.4
diff options
context:
space:
mode:
Diffstat (limited to 'man4/st.4')
-rw-r--r--man4/st.428
1 files changed, 14 insertions, 14 deletions
diff --git a/man4/st.4 b/man4/st.4
index 3dd16d744..44e90bee2 100644
--- a/man4/st.4
+++ b/man4/st.4
@@ -107,7 +107,7 @@ For example, if the drive firmware selects fixed-block mode,
the tape device uses fixed-block mode.
The options can
be changed with explicit
-.BR ioctl (2)
+.MR ioctl 2
calls and remain in effect when the device is closed and reopened.
Setting the options affects both the auto-rewind and the nonrewind
device.
@@ -129,19 +129,19 @@ have nothing to do with disk partitions.
A partitioned tape can be
seen as several logical tapes within one medium.)
Partition support has to be enabled with an
-.BR ioctl (2).
+.MR ioctl 2 .
The tape
location is preserved within each partition across partition changes.
The partition used for subsequent tape operations is
selected with an
-.BR ioctl (2).
+.MR ioctl 2 .
The partition switch is executed together with
the next tape operation in order to avoid unnecessary tape
movement.
The maximum number of partitions on a tape is defined by a
compile-time constant (originally four).
The driver contains an
-.BR ioctl (2)
+.MR ioctl 2
that can format a tape with either one or two partitions.
.P
Device
@@ -208,7 +208,7 @@ read calls.
The third read returns an error.
.SS Ioctls
The driver supports three
-.BR ioctl (2)
+.MR ioctl 2
requests.
Requests not recognized by the
.B st
@@ -747,7 +747,7 @@ writing on the current medium type.
.TP
\fBGMT_ONLINE\fP(\fIx\fP)
The last
-.BR open (2)
+.MR open 2
found the drive with a tape in place and ready for operation.
.TP
\fBGMT_D_6250\fP(\fIx\fP)
@@ -826,7 +826,7 @@ struct mtpos {
.B EACCES
An attempt was made to write or erase a write-protected tape.
(This error is not detected during
-.BR open (2).)
+.MR open 2 .)
.TP
.B EBUSY
The device is already in use or the driver was unable to allocate a
@@ -838,7 +838,7 @@ process.
.TP
.B EINVAL
An
-.BR ioctl (2)
+.MR ioctl 2
had an invalid argument, or a requested block size was invalid.
.TP
.B EIO
@@ -846,7 +846,7 @@ The requested operation could not be completed.
.TP
.B ENOMEM
The byte count in
-.BR read (2)
+.MR read 2
is smaller than the next physical block on the tape.
(Before Linux 2.2.18 and Linux 2.4.0 the extra bytes have been
.\" Precisely: Linux 2.6.0-test6
@@ -858,7 +858,7 @@ end-of-medium.
.TP
.B ENOSYS
Unknown
-.BR ioctl (2).
+.MR ioctl 2 .
.TP
.B ENXIO
During opening, the tape device does not exist.
@@ -908,7 +908,7 @@ this is that a fairly large tape block size has to be used to get
acceptable data transfer rates on the SCSI bus.
.IP \[bu]
Many programs (e.g.,
-.BR tar (1))
+.MR tar 1 )
allow the user to specify the blocking
factor on the command line.
Note that this determines the physical block
@@ -928,9 +928,9 @@ if verbose SCSI messages are enabled in kernel configuration.
.IP \[bu]
The driver's internal buffering allows good throughput in fixed-block
mode also with small
-.BR read (2)
+.MR read 2
and
-.BR write (2)
+.MR write 2
byte counts.
With direct transfers
this is not possible and may cause a surprise when moving to the 2.6
@@ -939,7 +939,7 @@ The solution is to tell the software to use larger transfers (often
telling it to use larger blocks).
If this is not possible, direct transfers can be disabled.
.SH SEE ALSO
-.BR mt (1)
+.MR mt 1
.P
The file
.I drivers/scsi/README.st