From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 11:20:35 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 589B816A4B3 for ; Tue, 16 Sep 2003 11:20:35 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 02DA643FFB for ; Tue, 16 Sep 2003 11:20:07 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 9640 invoked by uid 1000); 16 Sep 2003 18:20:08 -0000 Date: Tue, 16 Sep 2003 11:20:08 -0700 (PDT) From: Nate Lawson To: Dan Langille In-Reply-To: <3F660F32.17694.2490D2C@localhost> Message-ID: <20030916111926.N9364@root.org> References: <3F660F32.17694.2490D2C@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: scsi@freebsd.org Subject: Re: is MinBlock == MaxBlock common? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 18:20:35 -0000 On Mon, 15 Sep 2003, Dan Langille wrote: > How common is it for a device to have a MinBlock == MaxBlock as in > the following? > > I ask this because this is what it showing up after I patched my > sa(4). See > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=43376+0+current/freebsd- > scsi for details. > > # /usr/local/sbin/tapeinfo -f /dev/pass0 > Product Type: Tape Drive > Vendor ID: 'WANGTEK ' > Product ID: '51000 SCSI M74H' > Revision: '12B3' > Attached Changer: Yes > MinBlock:512 > MaxBlock:512 > Ready: yes Since you effectively hard-coded the blocksize to 512 using the quirk, you're just getting that value sent back to you, not the actual device MODE SENSE page. -Nate