From owner-freebsd-scsi Tue Jan 12 00:54:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18742 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 00:54:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18737 for ; Tue, 12 Jan 1999 00:54:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id AAA22389; Tue, 12 Jan 1999 00:53:29 -0800 Date: Tue, 12 Jan 1999 00:53:29 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home cc: scsi@FreeBSD.ORG Subject: Re: CAM SA Problem (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is all pretty wierd. I can't figure out why the prevent/allow is happening twice, nor can I figure out what's happening with the space operation. I *will* say that the current sa driver has retries set for many operations that it shouldn't, in fact, retry (saspace is one of them)- but not for saprevent. In either case, a retry is masking some other error. Try it with camcontol -Ic device which should have saerror dump unconditionally the sense key, asc, etc... Sigh. I was going to try and get this all cleaned up before the code fork this week, but doubt I'll make it. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message