From owner-freebsd-bugs  Tue Nov 21 08:50:08 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA04794
          for bugs-outgoing; Tue, 21 Nov 1995 08:50:08 -0800
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA04787
          ; Tue, 21 Nov 1995 08:50:03 -0800
Date: Tue, 21 Nov 1995 08:50:03 -0800
Message-Id: <199511211650.IAA04787@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Nate Williams <nate@rocky.sri.MT.net>
Subject: Re: i386/832: 4mm DAT drive errors
Reply-To: Nate Williams <nate@rocky.sri.MT.net>
Sender: owner-bugs@FreeBSD.ORG
Precedence: bulk

The following reply was made to PR i386/832; it has been noted by GNATS.

From: Nate Williams <nate@rocky.sri.MT.net>
To: green@aries.isf.rl.af.mil
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: i386/832: 4mm DAT drive errors
Date: Tue, 21 Nov 1995 09:49:14 -0700

 Charles Kenneth Green writes:
 > 
 > >Number:         832
 > >Category:       i386
 > >Synopsis:       Tape drive busy errors - dump aborts
 > (ahc0:4:0): "ARCHIVE Python 28454-XXX 4ASB" type 1 removable SCSI 2
 > st0(ahc0:4:0): Sequential-Access density code 0x8c, 512-byte blocks, write-enabled
 
 
 > 
 > 
 > >Description:
 > 
 > When trying to do backups to my FreeBSD 2.1 system my 4mm 5gig Python
 > tape drive reports "st0(ahc0:4:0): Target Busy" numerous times and
 > then aborts the dump.
 > 	I've tried replacing the cable but that hasn't had any
 > positive affect.
 > 
 > >How-To-Repeat:
 > 
 >  	Send a large dump to the tape drive.
 
 Hmm, here is the output from my ARCHIVE 4mm
 
 (aha0:6:0): "ARCHIVE Python 25588-XXX 2.96" type 1 removable SCSI 2
 st0(aha0:6:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled
 
 I've done quite a few dumps (and one restore even) with my tape drive on
 2.1-stable w/out any problems.
 
 
 Nate