--q9KOos5vDmpwPx9o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 26, 2006 at 05:50:55AM -0600, John R. Shannon wrote:
> I setup a iSCSI server on a NetBSD-CURRENT Xen domainU. My=20
> /etc/iscsi/targets file has:
>=20
> # extent        file or device          start           length
> extent0         /dev/xbd1a              0               38156MB
> extent1         /dev/xbd2a              0               38156MB
> extent2         /dev/xbd3a              0               38156MB
>=20
> # target        flags   storage         netmask
> target0         rw      extent0         10.1.1.2/32
> target1         rw      extent1         10.1.1.3/32
> target2         rw      extent2         10.1.1.4/32
>=20
> Using an open-isci initiator on Linux, I'm able to discover the targets:
>=20
> [root@g1 init.d]# iscsiadm -m discovery --type sendtargets --portal 10.1.=
1.3
> [b24591] 10.1.1.3:3260,1 iqn.1994-04.org.netbsd.iscsi-target:target1
> [b24590] 10.1.1.3:3260,1 iqn.1994-04.org.netbsd.iscsi-target:target0
> [b24592] 10.1.1.3:3260,1 iqn.1994-04.org.netbsd.iscsi-target:target2
>=20
> and login:
> [root@g1 init.d]# iscsiadm -m node --record=3Db24590 --login
> [root@g1 init.d]# iscsiadm
> [00:b24590] 10.1.1.3:3260,1 iqn.1994-04.org.netbsd.iscsi-target:target0
>=20
> However, the initiator is unhappy with the LUN (from dmesg):
>=20
> SCSI subsystem initialized
> iscsi: registered transport (tcp)
> scsi0 : iSCSI Initiator over TCP/IP, v.0.3
>   Vendor: NetBSD    Model: NetBSD/Intel iS   Rev: 0
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> scsi: host 0 channel 0 id 0 lun 0x4e65744253440000 has a LUN larger than=
=20
> currently supported.
> scsi: host 0 channel 0 id 0 lun 0x4e65744253442f49 has a LUN larger than=
=20
> currently supported.
> scsi: host 0 channel 0 id 0 lun 0x6e74656c20695300 has a LUN larger than=
=20
> currently supported.
> scsi: host 0 channel 0 id 0 lun12288 has a LUN larger than allowed by=20
> the host adapter
>=20
> 1) Does this LUN look correct?
> 2) If so, is there any control over it?

I recommend getting an ethereal/tcpdump trace of the login.

Take care,

Bill

--q9KOos5vDmpwPx9o
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFET8auWz+3JHUci9cRArCXAKCI3Hi4RTcKDTuNC1/SFoidm4pSMQCdEWui
PSr7zkA8m4C6aKu7EwI7KDI=
=s+hG
-----END PGP SIGNATURE-----

--q9KOos5vDmpwPx9o--