From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 16:13:21 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 8C42516A4B3 for ; Mon, 15 Sep 2003 16:13:21 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96A9943FB1 for ; Mon, 15 Sep 2003 16:13:20 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 825303D28 for ; Mon, 15 Sep 2003 19:13:12 -0400 (EDT) From: "Dan Langille" To: scsi@freebsd.org Date: Mon, 15 Sep 2003 19:12:50 -0400 MIME-Version: 1.0 Message-ID: <3F660F32.17694.2490D2C@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: 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: Mon, 15 Sep 2003 23:13:21 -0000 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 And from dmesg: sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI- CCS device sa0: 3.300MB/s transfers Thanks -- Dan Langille : http://www.langille.org/