Messages in this thread | | | Date | Fri, 8 Jan 1999 21:07:52 -0600 | From | John Goerzen <> | Subject | Re: [BUG] Tape access broken in 2.2.0pre |
| |
Oops, forgot to send this to the list.
On Fri, Jan 08, 1999 at 02:32:30PM +0100, Harald Koenig wrote:
> this write error can also happen when your EXABYTE is not using variable blocks > (block size 0) and you are (cat is) trying to write blocks which are not > integer multiples of the tape block size. > check the output of `mt stat' or similar, maybe someone changed the setting > of your drive ?!
Interesting:
drive type = Generic SCSI-2 tape drive status = 1024 sense key error = 0 residue count = 0 file number = -1 block number = -1 Tape block size 1024 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (1010000): ONLINE IM_REP_EN
I tried mt setblk 0. That fixed the problem. But:
1. Why do I need to do this now when I didn't have to do so before?
2. What exactly does this control?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |