From owner-freebsd-current  Tue Apr 18 09:07:49 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id JAA10319
          for current-outgoing; Tue, 18 Apr 1995 09:07:49 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA10313
          for <current@freebsd.org>; Tue, 18 Apr 1995 09:07:46 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id MAA15803 for current@freebsd.org; Tue, 18 Apr 1995 12:09:49 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199504181609.MAA15803@ns1.win.net>
Subject: re: DAT tape problems
To: current@FreeBSD.org
Date: Tue, 18 Apr 1995 12:09:48 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 949       
Sender: current-owner@FreeBSD.org
Precedence: bulk

> From: Doug Rabson <dfr@render.com>
> 
> 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?

I am using one here with success and have not seen this problem.  I have
been using it since the first snap (not on 2.0R).

I am running 3/22 snap now, not -current.

I have noticed a problem with the last file on the tape.  Could this be
what you are seeing?  I have placed a dummy file as the last file to be
backed up to get around this issue.  

My controller is a BT946C.

Regards,

Mark Hittinger
bugs@win.net