From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 23 02:08:38 2005 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 9794D16A4CE for ; Wed, 23 Feb 2005 02:08:38 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C505E43D41 for ; Wed, 23 Feb 2005 02:08:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j1N28fc3051786; Tue, 22 Feb 2005 19:08:41 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <421BE528.1050108@samsco.org> Date: Tue, 22 Feb 2005 19:06:32 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED, MANY_EXCLAMATIONS autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: scsi@freebsd.org Subject: Re: and now it's walking! Re: iSCSI first steps! 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: Wed, 23 Feb 2005 02:08:38 -0000 Danny Braniss wrote: > so now it's a maraton? > scbus3 is the iscsi: > > shuttle-2# camcontrol devlist > at scbus2 target 0 lun 0 (cd0,pass0) > at scbus3 target 0 lun 0 (pass1,da0) > < > at scbus3 target 0 lun 1 (pass2) > < > at scbus3 target 0 lun 2 (pass3) > < > at scbus3 target 0 lun 3 (pass4) > at scbus3 target 1 lun 0 (pass5,da1) > at scbus3 target 2 lun 0 (pass6,da2) > at scbus3 target 2 lun 1 (pass7,da3) > at scbus3 target 2 lun 2 (pass8,da4) > at scbus3 target 2 lun 3 (pass9,da5) > > and > shuttle-2# ls -ls /dev/da* > 0 crw-r----- 1 root operator 4, 25 Feb 22 16:30 /dev/da0 > 0 crw-r----- 1 root operator 4, 26 Feb 22 16:30 /dev/da1 > 0 crw-r----- 1 root operator 4, 27 Feb 22 16:30 /dev/da2 > 0 crw-r----- 1 root operator 4, 28 Feb 22 16:30 /dev/da3 > 0 crw-r----- 1 root operator 4, 29 Feb 22 16:30 /dev/da4 > 0 crw-r----- 1 root operator 4, 30 Feb 22 16:30 /dev/da5 > > so here is my question/dilema: from the 'camcontrol devlist' one can find > out some info as to the target, but not the targetaddress/targetname, which > were used to stablish the connection. this info is passed to the iscsi > driver, but it has no idea at to what kind of devices are being attached - > it can be a disk/tape/scanner/etc. > in short, the CAM has no idea about targetname/targetaddress, the iscsi > driver has no idea as to targets. Any ideas? > > danny > > > The inquiry information that the device returns will say what kind of device it is. As for the iscsi-specific information, you're correct that CAM really has no concept of it. Scott