From owner-freebsd-scsi Mon Sep 21 21:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11418 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 21:31:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11411 for ; Mon, 21 Sep 1998 21:31:07 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA06949; Mon, 21 Sep 1998 22:24:08 -0600 (MDT) Date: Mon, 21 Sep 1998 22:24:08 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809220424.WAA06949@narnia.plutotech.com> To: Wilko Bulte cc: scsi@FreeBSD.ORG Subject: Re: ncr - new log messages appearing Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809212154.XAA02617@yedi.iaf.nl> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809212154.XAA02617@yedi.iaf.nl> you wrote: > There is one thing that must be kept in mind for those RAID boxes: you might > encounter a QUEUE FULL even when that particular LUN had no I/O outstanding. > Other I/O on different LUNs in that case has used up all tags from the pool. > > I've seen drivers choke on this before ;-) CAM treats this as if we saw BUSY instead of QUEUE FULL. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message