Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!bug.rahul.net!rahul.net!a2i!genmagic!sgigate.sgi.com!news.tamu.edu!cs.utexas.edu!geraldo.cc.utexas.edu!piglet.cc.utexas.edu!not-for-mail
From: nichols@ccwf.cc.utexas.edu (Stewart Nichols)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 4mm DAT will TAR, but not DUMP.
Date: 28 Jun 1996 10:26:26 -0500
Organization: The University of Texas at Austin
Lines: 39
Message-ID: <4r0tj2$e39@piglet.cc.utexas.edu>
NNTP-Posting-Host: piglet.cc.utexas.edu
I have an Exabyte EXB-4200T 4mm DAT (yes DAT, not 8mm) scsi tape drive
that is unable to handle dumps. I can tar to the drive, then read
the tar with no problem, but a dump hangs the machine. Completely.
(The only thing that the computer will respond to is using ALT-{F1,F2,F3}
to another console - but no cursor is displayed on the alternate
consoles and nothing else can be done with the machine.)
The scsi controller is an adaptec 1522A. (not set for DMA)
I tried placing a DEC TLZ06 DAT drive in its place and the TLZ06
handles the dumps without any problems.
The Exabyte:
Jun 26 15:31:04 aspirin /kernel: (aic0:5:0): "EXABYTE EXB-4200 " type 1
removable SCSI 2
Jun 26 15:31:04 aspirin /kernel: st0(aic0:5:0): Sequential-Access density
code 0x13, 512-byte blocks, write-enabled
The DEC TLZ06:
Jun 26 21:15:41 aspirin /kernel: (aic0:5:0): "DEC TLZ06 (C)DEC 0491"
type 1 removable SCSI 2
Jun 26 21:15:41 aspirin /kernel: st0(aic0:5:0): Sequential-Access density
code 0x13, variable blocks, write-enabled
Notice that the Exabyte appears to be fixed-size 512byte blocks.
So I tried passing the block size to dump, but the machine hung
again, anyway.
I was able to write Windows NT backups with the Exabyte drive and read
them with the TLZ06 without problem. And, as I said, I can write tars
to the Exabyte drive and read them back without problem.
How do I fix/get-around this problem?
stu
nichols@ccwf.cc.utexas.edu