Re: RHEL 5.2, iscsi discovered as a generic device sg

2008-08-21 Thread Chris 

Never mind!  I figured out the issue - fat finger mistake in the
mask!  Sorry for the bogus traffic.

Cheers,
Chris

On Aug 21, 2:29 pm, Chris <[EMAIL PROTECTED]> wrote:
> It is loaded, that's the only way to get my scsi disks to show up
> (which work fine).  Its just in iscsi setup that seems to go awry.
>
> Any other suggestions?
>
> Cheers,
> Chris
>
> On Aug 21, 1:56 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> > Chris wrote:
> > > I am trying to get iscsi to work with my emc box.  When attempting to
> > > login, iscsid thinks the iscsi targets are of a generic typ sg
> > > rather than a scsi disk device.  Attached is the iscsid run in the
> > > foreground at debug level 9 and my iscsi.conf and version
>
> > open-iscsi does not think one or the other. It is too dumb :) The scsi
> > layer handles this. Make sure you have sd_mod load when you run this.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---

Re: RHEL 5.2, iscsi discovered as a generic device sg

2008-08-21 Thread Chris 

It is loaded, that's the only way to get my scsi disks to show up
(which work fine).  Its just in iscsi setup that seems to go awry.

Any other suggestions?

Cheers,
Chris


On Aug 21, 1:56 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
> Chris wrote:
> > I am trying to get iscsi to work with my emc box.  When attempting to
> > login, iscsid thinks the iscsi targets are of a generic typ sg
> > rather than a scsi disk device.  Attached is the iscsid run in the
> > foreground at debug level 9 and my iscsi.conf and version
>
> open-iscsi does not think one or the other. It is too dumb :) The scsi
> layer handles this. Make sure you have sd_mod load when you run this.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---

Re: RHEL 5.2, iscsi discovered as a generic device sg

2008-08-21 Thread Mike Christie 

Chris wrote:
> I am trying to get iscsi to work with my emc box.  When attempting to
> login, iscsid thinks the iscsi targets are of a generic typ sg
> rather than a scsi disk device.  Attached is the iscsid run in the
> foreground at debug level 9 and my iscsi.conf and version

open-iscsi does not think one or the other. It is too dumb :) The scsi 
layer handles this. Make sure you have sd_mod load when you run this.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---

RHEL 5.2, iscsi discovered as a generic device sg

2008-08-21 Thread Chris 

I am trying to get iscsi to work with my emc box.  When attempting to
login, iscsid thinks the iscsi targets are of a generic typ sg
rather than a scsi disk device.  Attached is the iscsid run in the
foreground at debug level 9 and my iscsi.conf and version

Thanks a bunch for any help in understanding this problem.

Cheers,
Chris


> RHEL 5.2
> 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 
> GNU/Linux
> transport class version 2.0-724. iscsid version 2.0-868

> command line: iscsiadm -m node -T iqn.1992-05.com.emc:apm00081900975-22 
> -p 10.100.8.45:3260 -l

Output of iscsid run in foreground with debug set at level 9:
/sbin/iscsid -f -d 9
iscsid: transport class version 2.0-724. iscsid version 2.0-868
iscsid: in ctldev_open
iscsid: created NETLINK_ISCSI socket...
iscsid: InitiatorName==iqn.1994-05.com.redhat:b71d38cd8ea2
iscsid: InitiatorName=iqn.1994-05.com.redhat:b71d38cd8ea2
iscsid: InitiatorAlias=pprod01
iscsid: in ctldev_closeiscsid: Max file limits 1024 1024
iscsid: reaped pid 31512, reap_count now 0
iscsid: poll result 1
iscsid: in read_transports
iscsid: Adding new transport iser
iscsid: Adding new transport tcp
iscsid: Matched transport tcp

iscsid: Allocted session 0x187c96f0
iscsid: no authentication configured...
iscsid: resolved 10.100.8.45 to 10.100.8.45
iscsid: get conn context 0x187d0d20
iscsid: set TCP recv window size to 524288, actually got 262142
iscsid: set TCP send window size to 524288, actually got 262142
iscsid: connecting to 10.100.8.45:3260
iscsid: sched conn context 0x187d0d20 event 2, tmo 0
iscsid: thread 0x187d0d20 schedule: delay 0 state 3
iscsid: Setting login timer 0x187cebd0 timeout 15
iscsid: thread 0x187cebd0 schedule: delay 60 state 3
iscsid: exec thread 187d0d20 callback
iscsid: put conn context 0x187d0d20
iscsid: connected local port 39540 to 10.100.8.45:3260
iscsid: in kcreate_session
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: in nlpayload_read
iscsid: created new iSCSI session 14
iscsid: in kcreate_conn
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: in nlpayload_read
iscsid: created new iSCSI connection 14:0
iscsid: in kbind_conn
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: in nlpayload_read
iscsid: bound iSCSI connection 14:0 to session 14
iscsid: sending login PDU with current stage 1, next stage 3, transit
0x80, isid 0x00023d0e exp_statsn 0
iscsid: >InitiatorName=iqn.1994-05.com.redhat:b71d38cd8ea2
iscsid: >InitiatorAlias=pprod01
iscsid: >TargetName=iqn.1992-05.com.emc:apm00081900975-22
iscsid: >SessionType=Normal
iscsid: >HeaderDigest=None,CRC32C
iscsid: >DataDigest=None
iscsid: >DefaultTime2Wait=2
iscsid: >DefaultTime2Retain=0
iscsid: >IFMarker=No
iscsid: >OFMarker=No
iscsid: >ErrorRecoveryLevel=0
iscsid: >InitialR2T=No
iscsid: >ImmediateData=Yes
iscsid: >MaxBurstLength=16776192
iscsid: >FirstBurstLength=262144
iscsid: >MaxOutstandingR2T=1
iscsid: >MaxConnections=1
iscsid: >DataPDUInOrder=Yes
iscsid: >DataSequenceInOrder=Yes
iscsid: >MaxRecvDataSegmentLength=131072
iscsid: in ksend_pdu_begin
iscsid: send PDU began for hdr 48 bytes and data 480 bytes
iscsid: in kwritev
iscsid: wrote 48 bytes of PDU header
iscsid: in kwritev
iscsid: wrote 480 bytes of PDU data
iscsid: in ksend_pdu_end
iscsid: in __kipc_call
iscsid: in kwritev
iscsid: in nlpayload_read
iscsid: in nlpayload_read
iscsid: send PDU finished for conn 14:0
iscsid: thread removed

iscsid: poll result 1
iscsid: in ctldev_handle
iscsid: in nl_read
iscsid: ctldev_handle got event type 101

iscsid: get conn context 0x187d0d20
iscsid: message real length is 480 bytes, recv_handle 0x187d2620
iscsid: in nlpayload_read
iscsid: sched conn context 0x187d0d20 event 1, tmo 0
iscsid: thread 0x187d0d20 schedule: delay 0 state 3
iscsid: thread 187cebd0 wait some more
iscsid: exec thread 187d0d20 callback
iscsid: in krecv_pdu_begin
iscsid: recv PDU began, pdu handle 0x0x187d2658
iscsid: in kread
iscsid: read 48 bytes of PDU header
iscsid: read 48 PDU header bytes, opcode 0x23, dlength 360, data
0x187cc7c0, max 8192
iscsid: in kread
iscsid: read 360 bytes of PDU data
iscsid: finished reading login PDU, 48 hdr, 0 ah, 360 data, 0 pad
iscsid: login current stage 1, next stage 3, transit 0x80
iscsid: >HeaderDigest=CRC32C
iscsid: >DataDigest=None
iscsid: >DefaultTime2Wait=2
iscsid: >DefaultTime2Retain=20
iscsid: >IFMarker=No
iscsid: >OFMarker=No
iscsid: >ErrorRecoveryLevel=0
iscsid: >InitialR2T=No
iscsid: >ImmediateData=Yes
iscsid: >MaxBurstLength=16776192
iscsid: >FirstBurstLength=262144
iscsid: >MaxOutstandingR2T=1
iscsid: >MaxConnections=1
iscsid: >DataPDUInOrder=Yes
iscsid: >DataSequenceInOrder=Yes
iscsid: >TargetAlias=VMware-qa02
iscsid: >TargetPortalGroupTag=1
iscsid: >MaxRecvDataSegmentLength=65536
iscsid: in krecv_pdu_end
iscsid: recv PD