From owner-freebsd-scsi Sat Apr 25 22:12:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15288 for freebsd-scsi-outgoing; Sat, 25 Apr 1998 22:12:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (mjacob@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15283 for ; Sat, 25 Apr 1998 22:12:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id WAA29259; Sat, 25 Apr 1998 22:07:12 -0700 Date: Sat, 25 Apr 1998 22:07:12 -0700 From: Matthew Jacob Message-Id: <199804260507.WAA29259@feral.com> To: gibbs@narnia.plutotech.com, julian@whistle.com Subject: Re: does CAM do this? Cc: Harlan.Stenn@pfcs.com, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I think the reason is because he doesn't understand the difference between >fixed and variable block modes. Exactly. > > >> The CAM driver behaves >> exactly as you wish. When a short read is encountered, the user >> is returned a short read. Just be aware, however, that if the device >> is in fixed block mode, your request must be a multiple of the block >> size. Should it be a multiple > 1, you will get more than a single >> block back. The only way to determine the block size in fixed block >> mode is to perform a smart search for the block size. > >I may be wrong but I vaguely remeber thet the 'info' field contains valid >information in this case which I USED to print out in a meaningful manner >in one version of st.c (possibly only the TFS version). Yes, for SILI errrors, the info field is the residual. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message