Lines Matching refs:tape
7 This file contains brief information about the SCSI tape driver.
18 to any specific tape drive. The tape parameters can be specified with
21 1. Each user can specify the tape parameters he/she wants to use
24 in a multiuser environment the next user finds the tape parameters in
27 2. The system manager (root) can define default values for some tape
30 new tape is loaded into the drive or if writing begins at the
31 beginning of the tape. The second method is applicable if the tape
32 drive performs auto-detection of the tape format well (like some
33 QIC-drives). The result is that any tape can be read, writing can be
35 the tape is rewritten from the beginning (or a new tape is written
57 between formats in multi-tape operations (the explicitly overridden
58 parameters are reset when a new tape is loaded).
64 supported devices. The Linux SCSI tape driver does not contain such
76 of the physical block on tape. When reading, the drive reads the next
77 tape block and returns to the user the data if the read() byte count
85 Support is provided for changing the tape partition and partitioning
86 of the tape with one or two partitions. By default support for
87 partitioned tape is disabled for each driver and it can be enabled
97 written to tape before the command returns. This makes sure that write errors
103 the program wants to close/open the tape device between files and wants to
106 If rewind, offline, bsf, or seek is done and previous tape operation was
107 write, a filemark is written before moving tape.
116 tape in the drive (commands trying to write something return error if
123 The tape driver currently supports up to 2^17 drives if 4 modes for
133 remaining bits define the tape device number. This numbering is
142 directories corresponding to the existing tape devices. There are autorewind
144 is the tape number and y a character corresponding to the mode (none, l, m,
145 a). For example, the directories for the first tape device are (assuming four
160 A link named 'tape' is made from the SCSI device directory to the class
167 The st driver maintains statistics for tape drives inside the sysfs filesystem.
180 pointing to the same tape drive use the same statistics. That means
189 to complete (including read and write). This includes tape movement
190 commands such as seeking between file or set marks and implicit tape
191 movement such as when rewind on close tape devices are used.
193 - The number of I/Os issued to the tape drive other than read or
197 - The number of bytes read from the tape drive.
199 - The number of read requests issued to the tape drive.
204 - The number of bytes written to the tape drive.
206 - The number of write requests issued to the tape drive.
213 is issuing a read larger thean the block size on tape. For write
214 not all data made it to tape.
222 value as iodone_cnt at the device level. The tape statistics only count
239 The user can choose between these two behaviours of the tape driver by
241 file being read is closed. The BSD semantics leaves the tape where it
242 currently is whereas the SYS V semantics moves the tape past the next
263 The size of the driver buffers is always at least one tape block. In fixed
279 Asynchronous writing. Writing the buffer contents to the tape is
281 at the next tape operation. Asynchronous writes are not done with
286 tape after the early-warning mark to flush the driver buffer.
344 tape drive if this is non-zero
384 The tape is positioned and the drive parameters are set with ioctls
385 defined in mtio.h The tape control program 'mt' uses these ioctls. Try
386 to find an mt that supports all of the Linux SCSI tape ioctls and
387 opens the device for writing if the tape contents will be modified
398 As above but tape positioned before filemark.
416 wait until data is on tape)
420 Rewind tape.
426 Re-tension tape.
430 Erase tape. If the argument is zero, the short erase command
434 Seek to tape block count. Uses Tandberg-compatible seek (QFA)
444 Explicitly lock/unlock the tape drive door.
446 Explicitly load and unload the tape. If the
449 drive with the command and it selects the tape slot to use of
460 Moves the tape to the partition given by the argument at the
461 next tape operation. The block at which the tape is positioned
462 is the block where the tape was previously positioned in the
463 new active partition unless the next tape operation is
464 MTSEEK. In this case the tape is moved directly to the block
468 Formats the tape with one partition (argument zero) or two
472 partition of the tape. If the argument is negative, its absolute
509 be used for repositioning the tape (global)
615 is set if there is no tape in the drive. GMT_EOD means either
616 end of recorded data or end of tape. GMT_EOT means end of tape.
625 The maximum number of tape devices is determined by the define
629 Immediate return from tape positioning SCSI commands can be enabled by
631 the next tape operation is not started before the previous one has
662 If the tape seems to hang, I would be very interested to hear where
664 of the process using the tape. If the state is D, the process is
673 real reason is that the tape firmware has got confused.