Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!chi-news.cic.net!io.org!van-bc!news.mindlink.net!agate!tfs.com!mailhub.tfs.com!julian From: julian@mailhub.tfs.com (Julian Elischer) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: TDC 4200 and FreeBSD Date: 30 Oct 1995 05:32:15 GMT Organization: TRW Financial Systems, Oakland, CA Lines: 55 Message-ID: <471o0v$oe2@times.tfs.com> References: <46v2oj$kd1@linet04.li.net> NNTP-Posting-Host: mailhub.tfs.com In article <46v2oj$kd1@linet04.li.net>, Saad M. Waraich <waraich@li.net> wrote: >I am trying to use a 2GB QIC tape drive, (Tandberg 4200) with FreeBSD-current >and I was wondering if someone could help me with some problems that I've >been having. > >1) dump(8) runs out of tape very quickly. I can't dump a 250 meg partition > even on three (150m) tapes. However I'm sure this is not a problem > related to my tape drive but rather concerns dump itself. Somehow I > need to tell it what kind of tape/drive I'm dumping on. I believe dump THINKS it has run out of tape, but the drive has a lot left to go. feed ti the appropriate args.. this is an FAQ but I don't use dump so ha ve no idea.. sorry >2) dump-ing to stdout and then piping it to dd works, but I use up almost > twice as much tape (which might mean that dump might not be a culprit > in (1)). My root partition is about 20 meg and I can dump it 3 times > before running out of a 150 Meg tape. dump doesn't believe that stdout has a limit (very smart) you will need to use a LARGE BLOCKSIZE on dd.. >3) After dumping as mentioned in (2), when I go back to beginning of > the tape, I can read the table of contents of the first dump. But > if I type this: > mt rew > mt fsf 1 > restore tf /dev/nrst0 > I still get the TOC for the first dump. Whereas if I do this: > mt rew > dd if=/dev/nrst0 of=/dev/null (to skip one file) > restore tf /dev/nrst0 > I am able to get the TOC for the second archive. hmm sounds wrong.. I would expect them to be the same and I wrote it.. :( >4) And then ther are times when after writing a dump, I go back to the > beginning of the tape and try to get a TOC or to read the file and > get absolutely nothing. > Can anyone explain to me what I'm doing wrong ? Or is there a problem > with the driver or drive ? hmm I really can't say what's wrong, but I admit that it sounds like a bug.. > One more thing: > 'mt status' returns default density as 0x0. That's ok 0 means 'drive default'