Date: Tue, 22 Feb 2005 17:32:47 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: Scott <scottl@samsco.org> Cc: scsi@freebsd.org Subject: Re: and now it's walking! Re: iSCSI first steps! Message-ID: <E1D3c1n-0003af-O4@cs1.cs.huji.ac.il> In-Reply-To: Your message of Mon, 21 Feb 2005 08:50:32 -0700 .
next in thread | raw e-mail | index | archive | help
so now it's a maraton? scbus3 is the iscsi: shuttle-2# camcontrol devlist <HL-DT-ST CD-ROM GCR-8523B 1.00> at scbus2 target 0 lun 0 (cd0,pass0) <Intransa IP5000 1> 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) <NETAPP LUN 0.2> at scbus3 target 1 lun 0 (pass5,da1) <LINUX ISCSI 0> at scbus3 target 2 lun 0 (pass6,da2) <LINUX ISCSI 0> at scbus3 target 2 lun 1 (pass7,da3) <LINUX ISCSI 0> at scbus3 target 2 lun 2 (pass8,da4) <LINUX ISCSI 0> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1D3c1n-0003af-O4>