From owner-freebsd-scsi Fri Mar 12 8:40:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0EBEA1533C for ; Fri, 12 Mar 1999 08:40:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id IAA00237; Fri, 12 Mar 1999 08:39:59 -0800 Date: Fri, 12 Mar 1999 08:39:59 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Stephen McKay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Strange SCSI QIC tape behaviour In-Reply-To: <199903121057.UAA24445@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > So, I removed the tape, and inserted it again. Same write failures. > > Then I set the blocksize back to variable. Wrote /kernel on to it with dd > and it succeeded, but wrote very slowly (38KB/s). So, I rewound it, set it > back to 1024 byte block size, and it worked like there had never been any > problem at all! > > So, is this the most bizarre drive on Earth, or perhaps are there bugs in > the SCSI tape driver that need addressing? At the very least, the fixed > block size for QIC tapes should be 1024 not 512 for densities above QIC-320. Yes, that's a bug for me to address. Where is this piece of information from? > > Tandberg has a nice SCSI manual for their drive (though it's hard to find > on their web site). Thus, I am armed with raw data, but no understanding > of the current code. > -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message