From owner-freebsd-scsi Sat Apr 25 13:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08452 for freebsd-scsi-outgoing; Sat, 25 Apr 1998 13:00:57 -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 NAA08446 for ; Sat, 25 Apr 1998 13:00:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id NAA28239; Sat, 25 Apr 1998 13:00:11 -0700 Date: Sat, 25 Apr 1998 13:00:11 -0700 From: Matthew Jacob Message-Id: <199804252000.NAA28239@feral.com> To: Harlan.Stenn@pfcs.com, louie@TransSys.COM Subject: Re: does CAM do this? Cc: dkelly@HiWAAY.net, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From owner-freebsd-scsi@FreeBSD.ORG Sat Apr 25 12:56:26 1998 > > >Perhaps I've come in the middle here, but typically you simply issue >a read(2) system call with as large a block size as you're willing or >able to accomodate. The byte count returned is the size of the tape >block which was actually read. This sort of scheme works even if every >block within a tape file is a different block size. If, and only if, the tape is in variable block mode. If it's in fixed block mode, and the tape driver hasn't set SILI (Suppress Incorrect Length Indicator) you get an error if the requested byte count doesn't match the tape block size. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message