From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 21 23:07:19 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D6D616A400 for ; Wed, 21 Feb 2007 23:07:19 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5DAAE13C49D for ; Wed, 21 Feb 2007 23:07:19 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l1LN5gHI001062 for ; Wed, 21 Feb 2007 16:05:42 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 21 Feb 2007 16:05:42 -0700 (MST) Message-Id: <20070221.160542.-169061472.imp@bsdimp.com> To: scsi@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 21 Feb 2007 16:05:42 -0700 (MST) Cc: Subject: Quirk for this? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2007 23:07:19 -0000 I have a umass device that lies about the size of the device: umass0: on uhub1 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 61MB (125441 512 byte sectors: 64H 32S/T 61C) However, when I plug it in with other umass devices, this is what I see: umass0: on uhub2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 61MB (125440 512 byte sectors: 64H 32S/T 61C) The 125440 number is what is reported by ata as well. Is there some way I can quirk this to not get a huge cascade of errors when the last sector is read by the tasting code? I didn't see any way when I was reading the code, but the quirks are scatter in a few different files and I might have missed something. Warner