home *** CD-ROM | disk | FTP | other *** search
- > > When I actually try to tar a file off to the drive I get the following
- > > (as a result of setting _scsi_debug)
- > > ixfer_out fail: l2040 i20 w-1
- >
- > Hm, where did you write that tape? DAT drives usually support variable
- > length records, and you can only read such tapes back using the same
- > blocking. I had right this problem when I was creating tapes under SunOS,
- > until I explicitly piped the tar to dd bs=512 of=/dev/rst0.
-
- This was writing from netbsd (tar cvf /dev/rst0 file)
-
- Here is the line in my Mountlist under amigados for BTN-handler
- Startup = "scsi.device/UN-4/BS-512/NB-128/BT-4"
- As I said, I can read and write under ados, and can read tapes
- written under ados.
-
- > The above
- > error message tells you that 2040 bytes off the last write command
- > were not transmitted, and that the write was aborted due to a timeout
- > (w being -1). You can try upping the timeout by poking a larger value
- > into scsi_wait_data (or was it scsi_data_wait..).
-
- Ok, I'll see if that does anything.
-
- >
- > > Some stuff is actually getting onto the tape. Because when I do a tar tvf
- > > of the tape, I get a listing of the file name, and then later I
- > > get an error about the file being short.
- >
- > Hm, how to do you write to the tape, if I may ask?
-
- tar cvf /dev/rst0 file
-
- When I thought only dump had a problem, I tried specifing densities and
- number of feet in the tape (using numbers recommended in comp.sys.hp),
- but I still got the error messages.
-
- > Hm, even my A3000/UX had a proto chip, and UX were definitly not among
- > the first sold A3000. I guess Commo once bought a gazillion of those
- > chips and is still trying to get rid of them that way .. :-)
-
- Well I think mine was one of the last 3000s. That could mean they
- were out of PROTOs already, or were desparate to get rid of them.
- I guess I'll have to take a look and see what it is next time I have
- her open.
-
-