From owner-freebsd-current Tue Apr 18 08:25:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09657 for current-outgoing; Tue, 18 Apr 1995 08:25:48 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA09651 for ; Tue, 18 Apr 1995 08:25:46 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id LAA00977; Tue, 18 Apr 1995 11:24:53 -0400 From: Peter Dufault Message-Id: <199504181524.LAA00977@hda.com> Subject: Re: DAT tape problems To: dfr@render.com (Doug Rabson) Date: Tue, 18 Apr 1995 11:24:53 -0400 (EDT) Cc: current@FreeBSD.org In-Reply-To: from "Doug Rabson" at Apr 18, 95 02:19:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1011 Sender: current-owner@FreeBSD.org Precedence: bulk Doug Rabson writes: > > 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? There seems to be a big problem with DAT support. We should put a WARNING someplace, maybe even at boot up in the driver, until it is fixed. This is about the third DAT bug report in a few weeks. I just did a full dump/restore of two big partitions with an Exabyte 8200 on -current, so it isn't a general tape problem. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267