I think this is a known bug in 2.0.X. The following message is from Kai
Mäkisara, maintainer of the SCSI tape driver:
| On Wed, 28 May 1997, Jan Echternach wrote:
| > There is a problem with taper not detecting the end of tape. With my
| > SCSI DAT drive and kernel 2.0.30, read() returns 0 only one time, and
| > all subsequent reads return EIO. It seems that ftape returns _two_
| > times 0, which taper handles correctly.
| >
| ...
| >
| > Do 2.1.x kernels return two times 0? If so, should 2.0.30 also return
| > two times 0 at end of tape?
| >
| What should happen, according to the BSD semantics, is this:
| - at filemark, the first read returns 0 bytes, the second read returns
| data from the next file
| - at EOD, the first and the second read return 0 bytes, the third returns
| error (-1)
| i.e., 2.1.x operates correctly.
|
| The EOD behaviour was fixed at 2.1.20. In principle, it should be fixed
| also at 2.0.31 but I think the risks are too big: fixing EOD behaviour
| may break something else (the fix from 2.1.20 can't be used directly).
|
| Kai
> A second question is: does it exist something like a non-rewinding tape
> device ?. This would be useful to append stuf to the same tape, for
> example
> do several tar to the same tape.
/dev/st0: rewinding
/dev/nst0: non-rewinding
-- Jan EchternachDelta Internet http://www.DInet.de/ Tel. +49 2932 91 6 161 Zeit UmZuDenken! Fax. +49 2932 91 6 230
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu