Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!rutgers!sri-spam!sri-unix!hplabs!decwrl!decvax!tektronix!uw-beaver!cornell!rochester!pt.cs.cmu.edu!andrew.cmu.edu!postman# From: postman#@andrew.cmu.edu.UUCP Newsgroups: comp.unix.questions Subject: Problems with a munged tar tape Message-ID: Date: Sat, 31-Jan-87 14:31:21 EST Article-I.D.: andrew.MS.V3.20.dk1z.80022301.ghostwheel.sun3.239.7 Posted: Sat Jan 31 14:31:21 1987 Date-Received: Sun, 1-Feb-87 15:45:32 EST Organization: Carnegie-Mellon University Lines: 13 ReSent-Date: Sat, 31 Jan 87 14:32:26 est ReSent-From: postman#@andrew.cmu.edu ReSent-To:nntp-xmit#@andrew.cmu.edu Return-path: To: outnews#ext.nn.comp.unix.questions@andrew.cmu.edu (Outbound News) I have a 6250 bpi tar tape containing about 50MB of files. (About 5 years worth of college stuff.) Unfortunately, it seems that someone trying to read it in from me munged the header as every time I read it, I get an EOF immediately and no amount of effort can get past it. Also, the tape now seems to think it's a 1600 bpi tape and not a 6250 bpi tape. I've tried using dd to get past it, and I've tried using combinations of fseek, lseek, read, et all. No luck. Only thing I've not tried is physically cutting the header off and seeing what happens. As that is rather final, I'd like to know if there are any other things I could try. Are there any services out there that recover munged tapes? -David Kovar