From owner-freebsd-bugs Wed Dec 18 16:10:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA14677 for bugs-outgoing; Wed, 18 Dec 1996 16:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA14666; Wed, 18 Dec 1996 16:10:01 -0800 (PST) Date: Wed, 18 Dec 1996 16:10:01 -0800 (PST) Message-Id: <199612190010.QAA14666@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Julian H. Stacey" Subject: Re: misc/2242: mt blocksize 512 in Release 2.1.6 install Reply-To: "Julian H. Stacey" Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR misc/2242; it has been noted by GNATS. From: "Julian H. Stacey" To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/2242: mt blocksize 512 in Release 2.1.6 install Date: Thu, 19 Dec 1996 01:07:48 +0100 Hi, Reference: > From: J Wunsch > Reply-to: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) > Subject: Re: misc/2242: mt blocksize 512 in Release 2.1.6 install > Date: Wed, 18 Dec 1996 23:40:24 +0100 (MET) > Message-id: <199612182240.XAA24266@uriah.heep.sax.de> > > As jhs@freebsd.org wrote: > > > Maybe we could have provision for a command of form > > mt blocksize 512 > > in the install ? > > There is one. It's in the `options' screen. > > The blocksize of 512 is only more optimal than the default for your > Tandberg (and only if you're using QIC-150 cartridges, things are > different for QIC-525 ones). To the contrary, it would really kill > performance (if not even making the installation totally impossible) > for almost all modern drives. > > This is merely a problem with the st driver not having a quirk record > for this particular drive, where (almost?) all Tandbergs require the > ST_Q_SNS_HELP quirk flag set in order to work correctly. > > Can you please confirm that the following patch obviates the > requirement to do an additional ``mt blocksize 512'' for the TDC3800 > and QIC-150 tapes? I'll build a kernel to test it, but I recall building a release flop is a horror story that needs CVS ? in which case I may have trouble creating a release type boot flop , particularly as I no longer have a working cvs tree as its outgrown my dedicated 300 M drive , I'll get back to you Joerg, thanks. > > Index: sys/scsi/scsiconf.c > =================================================================== > RCS file: /home/ncvs/src/sys/scsi/scsiconf.c,v > retrieving revision 1.72 > diff -u -u -r1.72 scsiconf.c > --- scsiconf.c 1996/12/14 09:57:04 1.72 > +++ scsiconf.c 1996/12/18 22:38:01 > @@ -286,6 +286,10 @@ > "st", SC_ONE_LU, ST_Q_NEEDS_PAGE_0, mode_tandberg3600 > }, > { > + T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "TANDBERG", " TDC 3800", " - *", > + "st", SC_ONE_LU, ST_Q_SNS_HLP|ST_Q_NEEDS_PAGE_0, mode_tandberg3 - 600 > + }, > + { > T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "TANDBERG", " TDC 42*", "* - ", > "st", SC_ONE_LU, ST_Q_SNS_HLP|ST_Q_NO_1024, mode_tandberg4200 > }, > > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > > Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/