From owner-freebsd-current Wed Apr 19 00:30:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA09645 for current-outgoing; Wed, 19 Apr 1995 00:30:14 -0700 Received: from nlsys.demon.co.uk (nlsys.demon.co.uk [158.152.125.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA09639 for ; Wed, 19 Apr 1995 00:30:11 -0700 Received: (from dfr@localhost) by nlsys.demon.co.uk (8.6.10/8.6.9) id IAA01119; Wed, 19 Apr 1995 08:21:09 +0100 Date: Wed, 19 Apr 1995 08:21:09 +0100 (BST) From: Doug Rabson To: Mark Hittinger cc: current@FreeBSD.org Subject: re: DAT tape problems In-Reply-To: <199504181609.MAA15803@ns1.win.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 18 Apr 1995, Mark Hittinger wrote: > > From: Doug Rabson > > > > 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. This was actually the second to last of about 6 files on the tape. > > My controller is a BT946C. 1542B -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891