Re: Should connection restored?

2008-05-09 Thread MAKHU

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 = 0x0001
end_request: I/O error, dev sdi, sector 0
sd 14:0:0:1: SCSI error: return code = 0x0001
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 = 0x0001
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 = 0x0001
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 = 0x0001
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 = 0x0001
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 = 0x0001
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 = 0x0001
end_request: I/O error, dev sdi, sector 16
sd 14:0:0:1: SCSI error: return code = 0x0001
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 = 0x0001
end_request: I/O error, dev sdi, sector 0

scsi14 : iSCSI Initiator over TCP/IP
>   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.


Should connection restored?

2008-05-08 Thread MAKHU

When target is logged in to an initiator and then either target/
initiator is restarted,connection is lost.

Should the connection be restored?
--~--~-~--~~~---~--~~
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: "State: blocked"..Disc becomes unusable after target restart

2008-05-08 Thread MAKHU

This was the log message generated during the process of
1. Initiator logged into target
2. Target machine "iscsi-target" daemon restarted
3. So Exported disk becomes unusable on initiator side.
--
> scsi5 : iSCSI Initiator over TCP/IP
>   Vendor: IET   Model: VIRTUAL-DISK  Rev: 0
>   Type:   Direct-Access  ANSI SCSI revision: 04
> SCSI device sdg: 2097152 512-byte hdwr sectors (1074 MB)
> sdg: Write Protect is off
> sdg: Mode Sense: 77 00 00 08
> SCSI device sdg: drive cache: write through
> SCSI device sdg: 2097152 512-byte hdwr sectors (1074 MB)
> sdg: Write Protect is off
> sdg: Mode Sense: 77 00 00 08
> SCSI device sdg: drive cache: write through
>  sdg: sdg1
> sd 5:0:0:0: Attached scsi disk sdg
> sd 5:0:0:0: Attached scsi generic sg6 type 0
>  connection4:0: iscsi: detected conn error (1011)
---

On May 8, 2:46 pm, MAKHU <[EMAIL PROTECTED]> wrote:
> One more question in context to previous one,
>
> When ISCSI Target is restarted, "/proc/net/iet/session" file changes
> with some major delay.
> And this delay is not same all the time.It is sometimes less and
> sometimes more.
>
> After this delay,sessions are restored.But disk exported by this
> target becomes unusable for the Initiator logged in ito it.
>
> But ISCSI Target restart is necessary for addition/deletion of targets/
> Lun changed to reflect.
>
> My aim is "Persistent Connection after target restart".Means disks
> should be in "running" state rather than "Blocked".
>
> On May 8, 1:06 pm, MAKHU <[EMAIL PROTECTED]> wrote:
>
> > 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 0}
>
> > ---
> > Output of "iscsiadm -m session -i" before Target restart..
>
> > Check last entry of state of "iqn.2008-04.com.qualexsystems
> > :Admin" as running.
>
> > [EMAIL PROTECTED] ~]# iscsiadm -m session -i
> > iscsiadm version 2.0-742
> > 
> > Session (sid 42) using module tcp:
> > 
> > TargetName: iqn.2008-04.com.qualexsystems:Tar1
> > Portal Group Tag: 1
> > Network Portal: 192.168.7.71:3260
> > iSCSI Connection State: LOGGED IN
> > Internal iscsid Session State: NO CHANGE
>
> > 
> > Negotiated iSCSI params:
> > 
> > HeaderDigest: CRC32C
> > DataDigest: CRC32C
> > MaxRecvDataSegmentLength: 8192
> > MaxXmitDataSegmentLength: 8192
> > FirstBurstLength: 65536
> > MaxBurstLength: 262144
> > ImmediateData: No
> > InitialR2T: Yes
> > MaxOutstandingR2T: 1
>
> > 
> > Attached SCSI devices:
> > 
> > Host Number: 43 State: running
>
> > scsi43 Channel 00 Id 0 Lun: 0
> > Attached scsi disk sdi  State: running
>
> > 
> > Session (sid 61) using module tcp:
> > 
> > TargetName: iqn.2008-04.com.qualexsystems:Admin
> > Portal Group Tag: 1
> > Network Portal: 192.168.7.173:3260
> > iSCSI Connection State: LOGGED IN
> > Internal iscsid Session State: NO CHANGE
>
> > 
> > Negotiated iSCSI params:
> > 
> > HeaderDigest: CRC32C
> > DataDigest: CRC32C
> > MaxRecvDataSegmentLength: 8192
> > MaxXmitDataSegmentLength: 8192
> > FirstBurstLength: 65536
> > MaxBurstLength: 262144
> > ImmediateData: No
> > InitialR2T: Yes
> > MaxOutstandingR2T: 1
>
> > 
> > Attached SCSI devices:
> > 
> > Host Number: 62 State: running
>
> > scsi62 Channel 00 Id 0 Lun: 0
> > Attached scsi disk sdj  State: running
> > --
>
> > When i restared "iscsi daemon" on target machine.
>
> > [EMAIL PROTECTE

Re: "State: blocked"..Disc becomes unusable after target restart

2008-05-08 Thread MAKHU

One more question in context to previous one,

When ISCSI Target is restarted, "/proc/net/iet/session" file changes
with some major delay.
And this delay is not same all the time.It is sometimes less and
sometimes more.

After this delay,sessions are restored.But disk exported by this
target becomes unusable for the Initiator logged in ito it.

But ISCSI Target restart is necessary for addition/deletion of targets/
Lun changed to reflect.

My aim is "Persistent Connection after target restart".Means disks
should be in "running" state rather than "Blocked".

On May 8, 1:06 pm, MAKHU <[EMAIL PROTECTED]> wrote:
> 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 0}
>
> ---
> Output of "iscsiadm -m session -i" before Target restart..
>
> Check last entry of state of "iqn.2008-04.com.qualexsystems
> :Admin" as running.
>
> [EMAIL PROTECTED] ~]# iscsiadm -m session -i
> iscsiadm version 2.0-742
> 
> Session (sid 42) using module tcp:
> 
> TargetName: iqn.2008-04.com.qualexsystems:Tar1
> Portal Group Tag: 1
> Network Portal: 192.168.7.71:3260
> iSCSI Connection State: LOGGED IN
> Internal iscsid Session State: NO CHANGE
>
> 
> Negotiated iSCSI params:
> 
> HeaderDigest: CRC32C
> DataDigest: CRC32C
> MaxRecvDataSegmentLength: 8192
> MaxXmitDataSegmentLength: 8192
> FirstBurstLength: 65536
> MaxBurstLength: 262144
> ImmediateData: No
> InitialR2T: Yes
> MaxOutstandingR2T: 1
>
> 
> Attached SCSI devices:
> 
> Host Number: 43 State: running
>
> scsi43 Channel 00 Id 0 Lun: 0
> Attached scsi disk sdi  State: running
>
> 
> Session (sid 61) using module tcp:
> 
> TargetName: iqn.2008-04.com.qualexsystems:Admin
> Portal Group Tag: 1
> Network Portal: 192.168.7.173:3260
> iSCSI Connection State: LOGGED IN
> Internal iscsid Session State: NO CHANGE
>
> 
> Negotiated iSCSI params:
> 
> HeaderDigest: CRC32C
> DataDigest: CRC32C
> MaxRecvDataSegmentLength: 8192
> MaxXmitDataSegmentLength: 8192
> FirstBurstLength: 65536
> MaxBurstLength: 262144
> ImmediateData: No
> InitialR2T: Yes
> MaxOutstandingR2T: 1
>
> 
> Attached SCSI devices:
> 
> Host Number: 62 State: running
>
> scsi62 Channel 00 Id 0 Lun: 0
> Attached scsi disk sdj  State: running
> --
>
> When i restared "iscsi daemon" on target machine.
>
> [EMAIL PROTECTED] ~]# iscsiadm -m session -i
> iscsiadm version 2.0-742
> 
> Session (sid 42) using module tcp:
> 
> TargetName: Tar1
> Portal Group Tag: 1
> Network Portal: 192.168.7.71:3260
> iSCSI Connection State: LOGGED IN
> Internal iscsid Session State: NO CHANGE
>
> 
> Negotiated iSCSI params:
> 
> HeaderDigest: CRC32C
> DataDigest: CRC32C
> MaxRecvDataSegmentLength: 8192
> MaxXmitDataSegmentLength: 8192
> FirstBurstLength: 65536
> MaxBurstLength: 262144
> ImmediateData: No
> InitialR2T: Yes
> MaxOutstandingR2T: 1
>
> 
> Attached SCSI devices:
> 
> Host Number: 43 State: running
>
> scsi43 Channel 00 Id 0 Lun: 0
> Attached scsi disk sdi  State: running
>
> 
> Session (sid 61) using module tcp:
> 
> TargetName: iqn.2008-04.com.qualexsystems:Admin
> Portal Group Tag: 1
> Network Portal: 192.168.7.173:3260
> 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
> MaxOu

Target Restart event

2008-05-08 Thread MAKHU

One more question in context to previous one,

When ISCSI Target is restarted, "/proc/net/iet/session" file changes
with some major delay.
And this delay is not same all the time.It is sometimes less and
sometimes more.

After this delay,sessions are restored.But disk exported by this
target becomes unusable for the Initiator logged in ito it.

But ISCSI Target restart is necessary for addition/deletion of targets/
Lun changed to reflect.

My aim is "Persistent Connection after target restart".Means disks
should be in "running" state rather than "Blocked".
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



"State: blocked"..Disc becomes unusable after target restart

2008-05-08 Thread MAKHU

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 0
}
---
Output of "iscsiadm -m session -i" before Target restart..

Check last entry of state of "iqn.2008-04.com.qualexsystems
:Admin" as running.

[EMAIL PROTECTED] ~]# iscsiadm -m session -i
iscsiadm version 2.0-742

Session (sid 42) using module tcp:

TargetName: iqn.2008-04.com.qualexsystems:Tar1
Portal Group Tag: 1
Network Portal: 192.168.7.71:3260
iSCSI Connection State: LOGGED IN
Internal iscsid Session State: NO CHANGE


Negotiated iSCSI params:

HeaderDigest: CRC32C
DataDigest: CRC32C
MaxRecvDataSegmentLength: 8192
MaxXmitDataSegmentLength: 8192
FirstBurstLength: 65536
MaxBurstLength: 262144
ImmediateData: No
InitialR2T: Yes
MaxOutstandingR2T: 1


Attached SCSI devices:

Host Number: 43 State: running

scsi43 Channel 00 Id 0 Lun: 0
Attached scsi disk sdi  State: running


Session (sid 61) using module tcp:

TargetName: iqn.2008-04.com.qualexsystems:Admin
Portal Group Tag: 1
Network Portal: 192.168.7.173:3260
iSCSI Connection State: LOGGED IN
Internal iscsid Session State: NO CHANGE


Negotiated iSCSI params:

HeaderDigest: CRC32C
DataDigest: CRC32C
MaxRecvDataSegmentLength: 8192
MaxXmitDataSegmentLength: 8192
FirstBurstLength: 65536
MaxBurstLength: 262144
ImmediateData: No
InitialR2T: Yes
MaxOutstandingR2T: 1


Attached SCSI devices:

Host Number: 62 State: running

scsi62 Channel 00 Id 0 Lun: 0
Attached scsi disk sdj  State: running
--

When i restared "iscsi daemon" on target machine.

[EMAIL PROTECTED] ~]# iscsiadm -m session -i
iscsiadm version 2.0-742

Session (sid 42) using module tcp:

TargetName: Tar1
Portal Group Tag: 1
Network Portal: 192.168.7.71:3260
iSCSI Connection State: LOGGED IN
Internal iscsid Session State: NO CHANGE


Negotiated iSCSI params:

HeaderDigest: CRC32C
DataDigest: CRC32C
MaxRecvDataSegmentLength: 8192
MaxXmitDataSegmentLength: 8192
FirstBurstLength: 65536
MaxBurstLength: 262144
ImmediateData: No
InitialR2T: Yes
MaxOutstandingR2T: 1


Attached SCSI devices:

Host Number: 43 State: running

scsi43 Channel 00 Id 0 Lun: 0
Attached scsi disk sdi  State: running


Session (sid 61) using module tcp:

TargetName: iqn.2008-04.com.qualexsystems:Admin
Portal Group Tag: 1
Network Portal: 192.168.7.173:3260
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: 62 State: running

scsi62 Channel 00 Id 0 Lun: 0
Attached scsi disk sdj  State: blocked

MY QUES. IS

After restarting target,Why disk becomes unused on the initiator side?
Though disk remains as logged in,but becomes unusable.
---
This was ur reply

Could you resend this to the list, with an explanation of what
restarting
iscsid means. Did you leave sessions running, kill iscsid, then
restart
iscsid? If so when iscsid starts up it syncs up the sessions. It shows
the
device as blocked and the session as not logged in, because for some
reason it cannot log back in (you would need to send some more log
output
to know why (maybe run iscsid with -d 8 when you restart it).

I had tried both "iscsid with -d 8" and latest "initiator-target" pair
as well.
Still the problem persists and disk becomes unusable after restarting
iscsi-target.

What can be the problem?Or Persistent connection is not possible.
--~--~-~--