home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.questions
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!destroyer!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!news
- From: sherwood@fenris.space.ualberta.ca (Sherwood Botsford)
- Subject: Re: tape problems
- Message-ID: <1992Jul29.160420.11533@kakwa.ucs.ualberta.ca>
- Sender: news@kakwa.ucs.ualberta.ca
- Nntp-Posting-Host: fenris.space.ualberta.ca
- Organization: University Of Alberta, Edmonton Canada
- References: <1992Jul29.012303.17033@kakwa.ucs.ualberta.ca>
- Date: Wed, 29 Jul 1992 16:04:20 GMT
- Lines: 33
-
- Ok, my original post was not informative enough. Several people pointed out
- that I didn't have a -c on the tar. That was a typo. Really.
-
- Try this again:
-
- The system is an Exabyte 8200 on a NextStation.
-
- This works
- cat filename > /dev/tapedevice
-
- This doesn't
- tar -cf /dev/tapedevice filespec
-
- Neither does this:
- tar -cf - filespec > /dev/tapedevice
-
- Opening the device in perl, and writing to it works however.
- The error I get is
-
- Jul 29 09:44:46 fenris mach: st: cmd = 0x1a sr_io_status = 2H
- Jul 29 09:44:46 fenris mach: Sense key = 0x3 Sense Code = 0x0
-
- Which translated: 1a = write 2H is check status
- 3 = unrecoverable media/blocking error.
-
- I picked up a utility on the net called mtset. This critter claims to be able
- to set fixed block/variable block, and make appropriate toggles of the report
- illegal length bit. I've tried both the logical and the illogical
- combinations, to no avail; except that I can get the tape drive to the point
- where cat doesn't work either.
-
- I think there is something I don't understand about the interaction between
- tape drivers and the device itself.
-