Print this page
12315 errors in section 7i of the manual

*** 96,106 **** to complete before disabling persistent error handling. Closing the device will also disable persistent error handling and clear any errors or exceptions. The Read Operation and Write Operation subsections contain more pertinent ! information reguarding persistent error handling. Read Operation The read(2) function reads the next record on the tape. The record size is passed back as the number of bytes read, provided it is not greater than the number requested. When a tape mark or end of data is read, a --- 96,106 ---- to complete before disabling persistent error handling. Closing the device will also disable persistent error handling and clear any errors or exceptions. The Read Operation and Write Operation subsections contain more pertinent ! information regarding persistent error handling. Read Operation The read(2) function reads the next record on the tape. The record size is passed back as the number of bytes read, provided it is not greater than the number requested. When a tape mark or end of data is read, a
*** 111,121 **** behavior, where another read will fetch the first record of the next tape file. If the BSD behavior is required, device names containing the letter `b' (for BSD behavior) in the final component should be used. If persistent error handling was enabled with either the BSD or SVR4 tape device behavior, all operations after this read error will return EIO ! errors until the MTIOCLRERR ioctl is issued. An MTFSF ioctl can then he issued. Two successful successive reads that both return zero byte counts indicate EOM on the tape. No further reading should be performed past the EOM. --- 111,121 ---- behavior, where another read will fetch the first record of the next tape file. If the BSD behavior is required, device names containing the letter `b' (for BSD behavior) in the final component should be used. If persistent error handling was enabled with either the BSD or SVR4 tape device behavior, all operations after this read error will return EIO ! errors until the MTIOCLRERR ioctl is issued. An MTFSF ioctl can then be issued. Two successful successive reads that both return zero byte counts indicate EOM on the tape. No further reading should be performed past the EOM.
*** 660,670 **** The MTIOCREADIGNOREEOFS ioctl enables or disables support for reading past double EOF marks which otherwise indicate End-Of-recorded-media (EOM) in the case of 1/2" reel tape drives. As an argument, it takes a pointer to an integer. If 0 (zero) is the specified integer, then double ! EOF marks indicate End-Of-recodred-media (EOD). If 1 is the specified integer, the double EOF marks no longer indicate EOM, thus allowing applications to read past two EOF marks. In this case it is the responsibility of the application to detect end-of-recorded-media (EOM). The specified tape behavior will be in effect until the device is closed. --- 660,670 ---- The MTIOCREADIGNOREEOFS ioctl enables or disables support for reading past double EOF marks which otherwise indicate End-Of-recorded-media (EOM) in the case of 1/2" reel tape drives. As an argument, it takes a pointer to an integer. If 0 (zero) is the specified integer, then double ! EOF marks indicate End-Of-recorded-media (EOD). If 1 is the specified integer, the double EOF marks no longer indicate EOM, thus allowing applications to read past two EOF marks. In this case it is the responsibility of the application to detect end-of-recorded-media (EOM). The specified tape behavior will be in effect until the device is closed.
*** 730,735 **** mt(1), tar(1), dd(1M), open(2), read(2), write(2), aioread(3C), aiowrite(3C), ar.h(3HEAD), st(7D) 1/4 Inch Tape Drive Tutorial ! illumos August 31, 2018 illumos --- 730,735 ---- mt(1), tar(1), dd(1M), open(2), read(2), write(2), aioread(3C), aiowrite(3C), ar.h(3HEAD), st(7D) 1/4 Inch Tape Drive Tutorial ! illumos February 17, 2020 illumos