Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1251 comp.os.386bsd.misc:729 comp.os.386bsd.questions:4538 Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.misc,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!menudo.uh.edu!lobster!nuchat!nyngate!gil From: gil@nynexdpi.com (Gil Kloepfer Jr) Subject: Re: Problem with CPIO? Organization: NYNEX DPI Company, Sugar Land, TX Followup-To: comp.os.386bsd.bugs Summary: Don't use ASCII headers References: <251oub$csf@manuel.anu.edu.au> Message-ID: <CC4pDz.3A7@nynexdpi.com> Date: Sat, 21 Aug 1993 21:36:57 GMT Lines: 25 In article <251oub$csf@manuel.anu.edu.au>, Mathew BM LIM <mbl900@anusf.anu.edu.au> wrote: >I can write to the drive without any apparent problems using > find / -print | cpio -ovBc > /dev/rst0 >All seems ok, the write finishes, but when I go to read the tape again, I get : > cpio -ivBct < /dev/rst0 [...] > cpio: Out of phase--get help Sigh...this has happened to me a gazillion times over and I think I finally found what it is. I haven't looked to see if I'm right or not. Since my system with the tape drive is in bad144-heaven right now, try doing your cpio *without* ASCII headers (remove the -c option). I had problems writing an ASCII-header cpio archive on *disk*. I believe it starts to barf when it sees a symbolic link. I have a feeling that somewhere along the line, symbolic links and ASCII headers don't work well together, but I could be completely off the deep end here. I finally got cpio to work fine when I wrote out the archives with binary headers (no -c option). Try this and let me know if it works. It did for me when making disk-based cpio archives. Gil. (gil@limbic.ssdl.com [home] gil@nynexdpi.com [work])