Hello All,

1. I am using latest "iscsitarget-0.4.16-1" from "sourceforge".

Now,can you tell whether it is expected to retain the connection with
initiator once the target is restarted?
-----------------------------------------------------------------
2. You wrote.

"The reason for having you do iscsid -d 8 was so we could see why we
cannot log back in"

   "iscsid -d 8" log messages can be seen from "dmesg"...right?

   check 2nd last line here in dmesg....."connection13:0: iscsi:
detected conn error (1011)"
---------------------------------------------------------------

iscsi: cmd 0x28 is not queued (7)
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 0
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 8
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 0
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 835576
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 835576
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 0
iscsi: cmd 0x28 is not queued (7)
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 8
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 16
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 0
iscsi: cmd 0x28 is not queued (7)
sd 14:0:0:1: SCSI error: return code = 0x00010000
end_request: I/O error, dev sdi, sector 0
----------------------------------------------------------------------------------------
scsi14 : iSCSI Initiator over TCP/IP

- Hide quoted text -
- Show quoted text -
>   Vendor: IET       Model: VIRTUAL-DISK      Rev: 0
>   Type:   Direct-Access                      ANSI SCSI revision: 04
> SCSI device sdh: 1048576 512-byte hdwr sectors (537 MB)
> sdh: Write Protect is off
> sdh: Mode Sense: 77 00 00 08
> SCSI device sdh: drive cache: write through
> SCSI device sdh: 1048576 512-byte hdwr sectors (537 MB)
> sdh: Write Protect is off
> sdh: Mode Sense: 77 00 00 08
> SCSI device sdh: drive cache: write through
>  sdh: sdh1
> sd 14:0:0:0: Attached scsi disk sdh
> sd 14:0:0:0: Attached scsi generic sg6 type 0
>   Vendor: IET       Model: VIRTUAL-DISK      Rev: 0
>   Type:   Direct-Access                      ANSI SCSI revision: 04
> SCSI device sdi: 835584 512-byte hdwr sectors (428 MB)
> sdi: Write Protect is off
> sdi: Mode Sense: 77 00 00 08
> SCSI device sdi: drive cache: write through
> SCSI device sdi: 835584 512-byte hdwr sectors (428 MB)
> sdi: Write Protect is off
> sdi: Mode Sense: 77 00 00 08
> SCSI device sdi: drive cache: write through
>  sdi: sdi1
> sd 14:0:0:1: Attached scsi disk sdi
> sd 14:0:0:1: Attached scsi generic sg7 type 0
>  connection13:0: iscsi: detected conn error (1011)

session13: iscsi: session recovery timed out after 120 secs
-----------------------------------------------------------------------
3. when session is recovered.....

[EMAIL PROTECTED] iscsi]# iscsiadm -m session -P 3
iSCSI Transport Class version 1.1-646
iscsiadm version 2.0-865
Target: iqn.2008-04.com.qualexsystems:Tar1
        Current Portal: 192.168.7.173:3260,1
        Persistent Portal: 192.168.7.173:3260,1
                **********
                Interface:
                **********
                Iface Name: default
                Iface Transport: tcp
                Iface IPaddress: default
                Iface HWaddress: default
                Iface Netdev: default
                SID: 13
                iSCSI Connection State: IN LOGIN
                Internal iscsid Session State: REPOEN
                ************************
                Negotiated iSCSI params:
                ************************
                HeaderDigest: None
                DataDigest: None
                MaxRecvDataSegmentLength: 8192
                MaxXmitDataSegmentLength: 8192
                FirstBurstLength: 65536
                MaxBurstLength: 262144
                ImmediateData: No
                InitialR2T: Yes
                MaxOutstandingR2T: 1
                ************************
                Attached SCSI devices:
                ************************
                Host Number: 14 State: running
                scsi14 Channel 00 Id 0 Lun: 0
                        Attached scsi disk sdh          State: running
                scsi14 Channel 00 Id 0 Lun: 1
                        Attached scsi disk sdi          State: running
----------------------------------------------------------------------------
Though Disk state is running,still "iSCSI Connection State: IN LOGIN".
So disks still becomes unusable.

Conclusion: What is moral of the story i got is that in our "target-
initiator" pair,Persistent connection is not possible.After target/
Initiator "iscsi-target" daemon restart(code given below),connection
is lost causing disks to be unusable.
-------------------------------------------------------
Note: Code for "iscsi-target" daemon restart
KVER=`uname -r`
MODPATH=/lib/modules/${KVER}/kernel/iscsi

stop() {
ietadm --op delete
killall ietd
rm -f /var/run/iscsi_trgt.pid
rmmod $MODPATH/iscsi_trgt
modprobe -r iscsi_trgt

}

start() {
modprobe iscsi_trgt
daemon /usr/sbin/ietd -d 8

}

restart() {
  stop
  start
}

--------------------------------------------------------
Thank you very much for helping me out..........................
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to