From owner-freebsd-scsi Wed Jun 17 07:28:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00596 for freebsd-scsi-outgoing; Wed, 17 Jun 1998 07:28:31 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (root@gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00586 for ; Wed, 17 Jun 1998 07:28:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id HAA06860; Wed, 17 Jun 1998 07:28:15 -0700 Message-ID: <3587D27F.71FA5B69@feral.com> Date: Wed, 17 Jun 1998 07:28:15 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: Peter Dufault CC: Dan Strick , freebsd-scsi@FreeBSD.ORG Subject: Re: the scsi pass through ioctl References: <199806170931.FAA15033@hda.hda.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Dufault wrote: > > I don't know of any reason and I did test it on active disks. > Harmless scsi commands should be fine. Any part of the system not > heavily used and not regression tested is likely to have problems > and should be used cautiously at first. Formatting disks, I/O > bypassing the buffer cache, and so on must be avoided... Even a TEST UNIT READY may put a device over it's tag limit. Some devices and host adapter drivers may not cope with this well, but, yes, this should mostly be okay. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message