From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 14 09:22:57 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0949E37B401 for ; Thu, 14 Aug 2003 09:22:57 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 82A7E43FDD for ; Thu, 14 Aug 2003 09:22:56 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 93608 invoked by uid 1000); 14 Aug 2003 16:22:57 -0000 Date: Thu, 14 Aug 2003 09:22:57 -0700 (PDT) From: Nate Lawson To: Chuck Tuffli In-Reply-To: <20030814011111.GB3594@cre85086tuf.rose.agilent.com> Message-ID: <20030814092214.C93571@root.org> References: <20030813034951.GA91644@panzer.kdm.org> <20030814011111.GB3594@cre85086tuf.rose.agilent.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: "Kenneth D. Merry" Subject: Re: problem running scsi_target X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 16:22:57 -0000 On Wed, 13 Aug 2003, Chuck Tuffli wrote: > Aside from the 2 fixes you mention below (without which bad things > happen), most of this was confusion on my part. I expected that isp(4) > would act as both target and initiator on a loop such that > > camcontrol rescan all > > on the machine running the target would have turned up the FreeBSD > Disk. Once I attached an initiator on a different box, I got the > expected > > # camcontrol devlist > ... > at scbus2 target 0 lun 0 (da1,pass1) > > I also didn't understand that "main loop beginning" meant that the > target was waiting for something. As soon as I did a rescan with the > other initiator, it was obvious scsi_target wasn't dead. > > Thanks for the help Ken! Glad to hear you got it working. I am planning to do some testing and finish the userland emulator at some point in the near future (next few months). -Nate