From owner-freebsd-scsi Tue Jun 1 1:52:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from firewall1.lehman.com (firewall.Lehman.COM [192.147.65.66]) by hub.freebsd.org (Postfix) with ESMTP id E89A3150E1 for ; Tue, 1 Jun 1999 01:52:41 -0700 (PDT) (envelope-from nclayton@lehman.com) Received: from relay.messaging-svcs2.lehman.com by firewall1.lehman.com (8.8.6/8.8.6) id EAA02015; Tue, 1 Jun 1999 04:52:40 -0400 (EDT) Received: from lonmailhost.lehman.com by relay.messaging-svcs2.lehman.com (8.9.3/8.8.5) id EAA25779; Tue, 1 Jun 1999 04:52:09 -0400 (EDT) Received: by lonmailhost.lehman.com (SMI-8.6/Lehman Bros. V1.5) id JAA00556; Tue, 1 Jun 1999 09:52:08 +0100 Message-ID: <19990601095207.S22307@lehman.com> Date: Tue, 1 Jun 1999 09:52:07 +0100 From: nclayton@lehman.com To: scsi@freebsd.org Subject: Tapes written on 2.2.8 not readable on 3.2 (was Re: PR docs/6681) References: <19990531090735.Q22307@lehman.com> <199905312210.WAA04171@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199905312210.WAA04171@jhs.muc.de>; from Julian Stacey on Tue, Jun 01, 1999 at 12:10:22AM +0200 Organization: Lehman Brothers Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi folks, I'm not on the SCSI list myself, I'm forwarding this on behalf of Julian Stacey. I've been closing doc PRs, including docs/6681, and contacted Julian to see if his PR was still relevant. In what follows, "> >" is my message to Julian, ">" is his reply. If any of you SCSI gurus has the time could you take a look at this? Cheers, N On Tue, Jun 01, 1999 at 12:10:22AM +0200, Julian Stacey wrote: > > It's this (from the PR); > > > > I suggest you append some of this info: > > > > (ncr0:5:0): "DEC TLZ06 (C)DEC 0389" type 1 removable SCSI 2 > > st0(ncr0:5:0): Sequential-Access > > st0(ncr0:5:0): 5.0 MB/s (200 ns, offset 8) > > density code 0x0, drive empty > > > > DAT drive, does 2 Gig with 90M tape, or more with compression on. > > SIngle slot height. > > Works on 2.2.8 > > > (ncr0:6:0): "TANDBERG TDC 3800 =04Y" type 1 removable SCSI 2 > > st1(ncr0:6:0): Sequential-Access > > st1(ncr0:6:0): asynchronous. > > density code 0x0, drive empty > > > > A 525 M QIC drive, > > reads 45 & 60M & 150M & 525M, > > writes 150 & 525, > > does variable block sizing by default > > (mt blocksize 512 to suppress that). > > Single slot height. > > Works on 2.2.8 > 3.2-RELEASE Seems to move the drive, but couldn't read tapes written > on 2.2.8 > > > (aha0:3:0): " " type 1 removable SCSI 1 > > st0(aha0:3:0): Sequential-Access density code 0x5, drive empty > > > > A Cipher QIC-24 SCSI, does 60 Meg > > Has a twist lever like a 5" floppy, & a pull out drawer. > > Double height ie 2 slots. > > Works on 2.2.8 > > > I know that the switch to CAM broke some stuff, but I'm not sure how > > extensive the breakage is -- if these aren't affected, and work with > > -stable/-current then I'll update the Handbook. > > I have 2 TANDBERG TDC 3800 drives, one on > > 3.2-RELEASE > sa0: Removable Sequential Access SCSI-2 device > sa0: 4.032MB/s transfers (4.032MHz, offset 7) > > one on > > 2.2.8-RELEASE > (ncr0:6:0): "TANDBERG TDC 3800 =04Y" type 1 removable SCSI 2 > st1(ncr0:6:0): Sequential-Access > st1(ncr0:6:0): asynchronous. > density code 0x0, drive empty > > Seems to me on brief experiment, > 3.2 can write data that 2.2.8 can read, > but 2.2.8 tapes are not readable on 3.2 system > (a disaster for anyone relying on backup tapes (not me thankfully)). > > Anyway, that was just a quick check, > maybe it's to do with the blocksize 512 stuff, > but looks like this is a problem. > > As I have 2 drives, 1 on 2.2.8 & 1 on 3.2, I may be uniquely useful > for test purposes for scsi team, feel free to pass my name along. > I am not worried about installing current on the 3.2 Tandberg box, > except that can't spare too much time for it. > I am not prepared to destabilise my other main 2.2.8 Tandberg box though :-) > > In light of this nasty suprise I have cancelled plan to upgrade my 2.2.8 > main system (that has the DEC TLZ06 DAT) until this problem is solved. > Once it's solved for Tandberg, I can try. > > The system with the Cipher QIC-24 will be upgraded to 3.2 in about 2 weeks. > & I can let you know about that. > > What was intended as a docu. upgrade has become a warning of peril :-) > Thanks, I'm glad to know, let me know if I can help, > feel free to cut/paste forward to scsi@ (not on that list myself). -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message