ST(4) | Device Drivers Manual | ST(4) |
st
— SCSI tape
driver
st* at scsibus?
#st0 at scsibus0 target 4 lun 0
(fixed-configuration
example)
The st
driver provides support for SCSI
tape drives. The device can have both a
raw
interface and a
block
interface; however, only the raw interface is usually used (or recommended).
The raw interface devices will have an ‘r’ in their names e.g.
/dev/rst0.
SCSI devices have a relatively high level interface and talk to the system via a SCSI adapter and a SCSI adapter driver e.g. ahc(4). The SCSI adapter must be separately configured into the system before a SCSI tape can be configured.
As the SCSI adapter is probed during boot, the
SCSI bus is scanned for devices. Any devices found which answer as
Sequential
type devices will be attached to the st
driver.
The st
driver is based around the concept
of a mount
session, which is defined as the period between the time that a tape
is mounted and the time when it is unmounted. Any parameters set during a
mount session remain in effect for the remainder of the session or until
replaced. The tape can be unmounted, bringing the session to a close in
several ways. These include:
Bit 0 of the minor number specifies whether a rewind is attempted when the device is closed. When it is set, the device will not attempt a rewind on close and the device will have an ‘n’ in its name. For example, /dev/rst0 will rewind on close but /dev/nrst0 will not.
Bit 1 of the minor number specifies whether an eject is attempted when the device is closed. When it is set, the device will attempt to eject its media on close and the device will have an ‘e’ in its name. For example, /dev/erst0 will eject its media on close but /dev/rst0 will not.
If both bit 0 and bit 1 are set then an eject will be attempted without a rewind and the device will have both an ‘e’ and an ‘n’ in its name. For example, /dev/enrst0 will eject its media without first rewinding it on close.
There is no guarantee that the attempted eject or rewind will be supported by the actual hardware.
SCSI tapes may run in either variable or fixed block-size modes. Most QIC-type devices run in fixed block-size mode, whereas most nine-track tapes and many new cartridge formats allow variable block-size. The difference between the two is as follows:
When reading a variable record/block from the tape, the head is logically considered to be immediately after the last item read, and before the next item after that. If the next item is a file mark, but it was never read, then the next process to read will immediately hit the file mark and receive an end-of-file notification.
If one requests more blocks than remain in the file, the drive
will encounter the file mark. Because there is some data to return
(unless there were no records before the file mark), the read will
succeed, returning that data. The next read will return immediately with
an EOF
. (As above, if the file mark is never
read, it remains for the next process to read if in no-rewind mode.)
The handling of file marks on write is automatic. If the user has written to the tape, and has not done a read since the last write, then a file mark will be written to the tape when the device is closed. If a rewind is requested after a write, then the driver assumes that the last file on the tape has been written, and ensures that there are two file marks written to the tape. The exception to this is that there seems to be a standard (which we follow, but don't understand why) that certain types of tape do not actually write two file marks to tape, but when read, report a “phantom” file mark when the last file is read. These devices include the QIC family of devices. (It might be that this set of devices is the same set as that of fixed. This has not yet been determined, and they are treated as separate behaviors by the driver at this time.)
The following
ioctl(2) calls apply to SCSI
tapes. Some also apply to other tapes. They are defined in the header file
<sys/mtio.h>
.
MTIOCGET
struct mtget *MTIOCTOP
struct mtop *
struct mtop { short mt_op; int mt_count; };
The following operation values are defined for mt_op:
MTWEOF
MTFSF
MTBSF
MTFSR
MTBSR
MTREW
MTOFFL
MTNOP
MTCACHE
MTNOCACHE
MTSETBSIZ
MTSETDNSTY
MTIOCIEOT
st
devices).MTIOCEEOT
st
devices).This st
driver was originally written for
Mach 2.5 by Julian Elischer, and was ported to
NetBSD by Charles Hannum. This man page was edited
for NetBSD by Jon Buller.
June 28, 2014 | OpenBSD-6.0 |