From owner-freebsd-current Tue Apr 18 10:10:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA12100 for current-outgoing; Tue, 18 Apr 1995 10:10:55 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA12091 for ; Tue, 18 Apr 1995 10:10:51 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA17946 (5.67b/IDA-1.5 for current@freebsd.org); Tue, 18 Apr 1995 19:10:29 +0200 Message-Id: <199504181710.AA17946@FileServ1.MI.Uni-Koeln.DE> From: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Tue, 18 Apr 1995 19:10:29 +0200 In-Reply-To: Doug Rabson "DAT tape problems" (Apr 18, 14:19) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Doug Rabson Subject: Re: DAT tape problems Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On Apr 18, 14:19, Doug Rabson wrote: } Subject: DAT tape problems } I just attempted to read back a dump from a DAT tape to test our backup } strategy and disturbingly, the file which read back from the tape was } corrupted. The directory was intact but when the dump was extracted, } there was a checksum error on one file and when comparing the extracted } tree with the original, at least one file had been corrupted. } } My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use } compression. Does anyone have an idea what is happening? DAT drives are supposed to work ! I'm using a HP 1533 DDS-2 drive with good success. What controller are you using ? There is special code in the NCR driver, that deals with certain DAT drives, which don't accept SCSI messages within an GETCC command. In case you are using this controller, your particular drive ID might need to be entered in some table in the driver. Most other controllers ought to deal with this in the controller firmware. Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706019 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln