From owner-freebsd-scsi Tue Jun 16 18:58:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12270 for freebsd-scsi-outgoing; Tue, 16 Jun 1998 18:58:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12265 for ; Tue, 16 Jun 1998 18:58:32 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id SAA20496; Tue, 16 Jun 1998 18:58:31 -0700 (PDT) Date: Tue, 16 Jun 1998 18:58:31 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199806170158.SAA20496@math.berkeley.edu> To: freebsd-scsi@FreeBSD.ORG Subject: the scsi pass through ioctl Cc: dan@math.berkeley.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 1) Can someone explain the timeout member of the scsireq struct used for the SCIOCCOMMAND (scsi command pass through) ioctl()? I would guess it sets the time period after which an incomplete scsi command will be cancelled without returning scsi status and that the SCCMD_TIMEOUT code will be returned in the retsts member of the scsireq struct. Can someone confirm this? Can someone tell me in what units the timeout is specified? Seconds? Milliseconds? Days? Endless Summers? 2) A long time ago someone said in a FreeBSD mailing list that you could trash your disk contents by attempting scsi pass through commands while the disk was also doing normal file system I/O. Does anyone recall why this might have been the case and know if it might still be the case? I can think of reasons why I might want to do "harmless" scsi commands on an active disk. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message