Re: iferror -38

2009-01-29 Thread chava45

Mike,
I tried to disable nops. But the issue still persists.
So what else can be the reason for this? It became show stopper.
Thanks
Chava

On Jan 28, 12:35 pm, Mike Christie micha...@cs.wisc.edu wrote:
 chava45wrote:
  Mike ,
  Can you also let me know if there is any workaround on this issue?

 Yeah, if this is the bug I thought I fixed then you can just turn off
 nops. Are you using dm-multipath? They are mostly useful for fast
 failovers when using multipath.

 You can turn them off by setting

 node.conn[0].timeo.noop_out_interval = 0
 node.conn[0].timeo.noop_out_timeout = 0

 in /etc/iscsi/iscsid.conf, then redoing the discovery command (iscsiadm
 -m discovery -t st -p ip).

 Or you can set this for already setup nodes by doing

 iscsiadm -m node -o update -n node.conn[0].timeo.noop_out_interval -v 0
 iscsiadm -m node -o update -n node.conn[0].timeo.noop_out_timeout -v 0

 (note if you do this you still want to set it in iscsid.conf so new
 targets that are discovered will get the new setting).



  On Jan 28, 10:42 am,chava45ssch...@gmail.com wrote:
  Mike ,
  In response to the following update by you...
  ---
  Either you are hitting the bug I thought I fixed or these nops are
  really timing out. I am downloading open filer now to test it out
  here.
  ---­­---
  Could you let me know once you test it? I am stuck up here and can not
  move forward with Oracle RAC installation on Oracle VM.
  Thanks
  Chava

  On Jan 28, 9:35 am, Mike Christie micha...@cs.wisc.edu wrote:

  chava45wrote:
  Mike,
  Here is the log information from /var/log/messages.
  ---­­­-
  Jan 27 14:02:04 rac1 iscsid: iSCSI logger with pid=4380 started!
  Jan 27 14:02:05 rac1 iscsid: transport class version 2.0-724. iscsid
  version 2.0-868
  Jan 27 14:02:05 rac1 iscsid: iSCSI daemon with pid=4381 started!
  Jan 27 14:03:02 rac1 kernel: scsi1 : iSCSI Initiator over TCP/IP
  Jan 27 14:03:03 rac1 kernel:   Vendor: OPNFILER  Model: VIRTUAL-
  DISK      Rev: 0
  Jan 27 14:03:03 rac1 kernel:   Type:   Direct-
  Access                      ANSI SCSI revision: 04
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
  sectors (537 MB)
  Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
  through
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
  sectors (537 MB)
  Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
  through
  Jan 27 14:03:03 rac1 iscsid: received iferror -38
  Jan 27 14:03:03 rac1 last message repeated 2 times
  Jan 27 14:03:03 rac1 iscsid: connection2:0 is operational now
  Jan 27 14:03:06 rac1 udevd-event[4401]: wait_for_sysfs: waiting for '/
  sys/devices/platform/host1/session2/target1:0:0/1:0:0:0/ioerr_cnt'
  failed
  Jan 27 14:03:13 rac1 kernel:  sda:3ping timeout of 5 secs expired,
  last rx 47558, last ping 48808, now 50058
  Either you are hitting the bug I thought I fixed or these nops are
  really timing out. I am downloading open filer now to test it out here.- 
  Hide quoted text -
  - Show quoted text -- Hide quoted text -
  - Show quoted text -- Hide quoted text -

 - Show quoted text -
--~--~-~--~~~---~--~~
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 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: iferror -38

2009-01-29 Thread chava45

Mike ,
What else could be the reason for it?
it became showstopper.

thanks
Chava
On Jan 28, 12:35 pm, Mike Christie micha...@cs.wisc.edu wrote:
 chava45 wrote:
  Mike ,
  Can you also let me know if there is any workaround on this issue?

 Yeah, if this is the bug I thought I fixed then you can just turn off
 nops. Are you using dm-multipath? They are mostly useful for fast
 failovers when using multipath.

 You can turn them off by setting

 node.conn[0].timeo.noop_out_interval = 0
 node.conn[0].timeo.noop_out_timeout = 0

 in /etc/iscsi/iscsid.conf, then redoing the discovery command (iscsiadm
 -m discovery -t st -p ip).

 Or you can set this for already setup nodes by doing

 iscsiadm -m node -o update -n node.conn[0].timeo.noop_out_interval -v 0
 iscsiadm -m node -o update -n node.conn[0].timeo.noop_out_timeout -v 0

 (note if you do this you still want to set it in iscsid.conf so new
 targets that are discovered will get the new setting).



  On Jan 28, 10:42 am, chava45 ssch...@gmail.com wrote:
  Mike ,
  In response to the following update by you...
  ---
  Either you are hitting the bug I thought I fixed or these nops are
  really timing out. I am downloading open filer now to test it out
  here.
  ---­­---
  Could you let me know once you test it? I am stuck up here and can not
  move forward with Oracle RAC installation on Oracle VM.
  Thanks
  Chava

  On Jan 28, 9:35 am, Mike Christie micha...@cs.wisc.edu wrote:

  chava45wrote:
  Mike,
  Here is the log information from /var/log/messages.
  ---­­­-
  Jan 27 14:02:04 rac1 iscsid: iSCSI logger with pid=4380 started!
  Jan 27 14:02:05 rac1 iscsid: transport class version 2.0-724. iscsid
  version 2.0-868
  Jan 27 14:02:05 rac1 iscsid: iSCSI daemon with pid=4381 started!
  Jan 27 14:03:02 rac1 kernel: scsi1 : iSCSI Initiator over TCP/IP
  Jan 27 14:03:03 rac1 kernel:   Vendor: OPNFILER  Model: VIRTUAL-
  DISK      Rev: 0
  Jan 27 14:03:03 rac1 kernel:   Type:   Direct-
  Access                      ANSI SCSI revision: 04
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
  sectors (537 MB)
  Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
  through
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
  sectors (537 MB)
  Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
  Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
  through
  Jan 27 14:03:03 rac1 iscsid: received iferror -38
  Jan 27 14:03:03 rac1 last message repeated 2 times
  Jan 27 14:03:03 rac1 iscsid: connection2:0 is operational now
  Jan 27 14:03:06 rac1 udevd-event[4401]: wait_for_sysfs: waiting for '/
  sys/devices/platform/host1/session2/target1:0:0/1:0:0:0/ioerr_cnt'
  failed
  Jan 27 14:03:13 rac1 kernel:  sda:3ping timeout of 5 secs expired,
  last rx 47558, last ping 48808, now 50058
  Either you are hitting the bug I thought I fixed or these nops are
  really timing out. I am downloading open filer now to test it out here.- 
  Hide quoted text -
  - Show quoted text -- Hide quoted text -
  - Show quoted text -- Hide quoted text -

 - Show quoted text -
--~--~-~--~~~---~--~~
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 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: iferror -38

2009-01-28 Thread chava45

Mike ,
Can you also let me know if there is any workaround on this issue?

On Jan 28, 10:42 am, chava45 ssch...@gmail.com wrote:
 Mike ,
 In response to the following update by you...
 ---
 Either you are hitting the bug I thought I fixed or these nops are
 really timing out. I am downloading open filer now to test it out
 here.
 ---­---
 Could you let me know once you test it? I am stuck up here and can not
 move forward with Oracle RAC installation on Oracle VM.
 Thanks
 Chava

 On Jan 28, 9:35 am, Mike Christie micha...@cs.wisc.edu wrote:



  chava45wrote:
   Mike,
   Here is the log information from /var/log/messages.
   ---­­-
   Jan 27 14:02:04 rac1 iscsid: iSCSI logger with pid=4380 started!
   Jan 27 14:02:05 rac1 iscsid: transport class version 2.0-724. iscsid
   version 2.0-868
   Jan 27 14:02:05 rac1 iscsid: iSCSI daemon with pid=4381 started!
   Jan 27 14:03:02 rac1 kernel: scsi1 : iSCSI Initiator over TCP/IP
   Jan 27 14:03:03 rac1 kernel:   Vendor: OPNFILER  Model: VIRTUAL-
   DISK      Rev: 0
   Jan 27 14:03:03 rac1 kernel:   Type:   Direct-
   Access                      ANSI SCSI revision: 04
   Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
   sectors (537 MB)
   Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
   Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
   through
   Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
   sectors (537 MB)
   Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
   Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
   through
   Jan 27 14:03:03 rac1 iscsid: received iferror -38
   Jan 27 14:03:03 rac1 last message repeated 2 times
   Jan 27 14:03:03 rac1 iscsid: connection2:0 is operational now
   Jan 27 14:03:06 rac1 udevd-event[4401]: wait_for_sysfs: waiting for '/
   sys/devices/platform/host1/session2/target1:0:0/1:0:0:0/ioerr_cnt'
   failed
   Jan 27 14:03:13 rac1 kernel:  sda:3ping timeout of 5 secs expired,
   last rx 47558, last ping 48808, now 50058

  Either you are hitting the bug I thought I fixed or these nops are
  really timing out. I am downloading open filer now to test it out here.- 
  Hide quoted text -

  - Show quoted text -- Hide quoted text -

 - Show quoted text -
--~--~-~--~~~---~--~~
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 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: iferror -38

2009-01-27 Thread chava45
 times
Jan 22 19:26:12 rac1 iscsid: connection1:0 is operational after
recovery (1 attempts)
Jan 22 19:26:21 rac1 kernel: ping timeout of 5 secs expired, last rx
5933, last ping 7183, now 8433
Jan 22 19:26:21 rac1 kernel:  connection1:0: iscsi: detected conn
error (1011)
Jan 22 19:26:22 rac1 iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Jan 22 19:26:25 rac1 iscsid: received iferror -38
Jan 22 19:26:25 rac1 last message repeated 2 times
Jan 22 19:26:25 rac1 iscsid: connection1:0 is operational after
recovery (1 attempts)
Jan 22 19:26:34 rac1 kernel: ping timeout of 5 secs expired, last rx
9189, last ping 10439, now 11689
Jan 22 19:26:34 rac1 kernel:  connection1:0: iscsi: detected conn
error (1011)
Jan 22 19:26:35 rac1 iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Jan 22 19:26:38 rac1 iscsid: received iferror -38
Jan 22 19:26:38 rac1 last message repeated 2 times
Jan 22 19:26:38 rac1 iscsid: connection1:0 is operational after
recovery (1 attempts)
Jan 22 19:26:47 rac1 kernel: ping timeout of 5 secs expired, last rx
12445, last ping 13695, now 14945
Jan 22 19:26:47 rac1 kernel:  connection1:0: iscsi: detected conn
error (1011)
Jan 22 19:26:48 rac1 iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Jan 22 19:26:51 rac1 iscsid: received iferror -38
Jan 22 19:26:51 rac1 last message repeated 2 times
Jan 22 19:26:51 rac1 iscsid: connection1:0 is operational after
recovery (1 attempts)
---­


and the output from iscsiadm -m session -P 3 is

iSCSI Transport Class version 2.0-724
iscsiadm version 2.0-868
Target: iqn.2006-01.com.openfiler:tsn.61b3375e9b1d
Current Portal: 10.98.1.101:3260,1
Persistent Portal: 10.98.1.101:3260,1
**
Interface:
**
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.1994-05.com.redhat:
54d4238c572
Iface IPaddress: 10.98.1.91
Iface HWaddress: default
Iface Netdev: default
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: Unknown
Internal iscsid Session State: NO CHANGE

Negotiated iSCSI params:

HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 131072
MaxXmitDataSegmentLength: 131072
FirstBurstLength: 262144
MaxBurstLength: 262144
ImmediateData: No
InitialR2T: Yes
MaxOutstandingR2T: 1

Attached SCSI devices:

Host Number: 0  State: running
scsi0 Channel 00 Id 0 Lun: 0
Attached scsi disk sda  State:
running
scsi0 Channel 00 Id 0 Lun: 1
scsi0 Channel 00 Id 0 Lun: 2
scsi0 Channel 00 Id 0 Lun: 3
scsi0 Channel 00 Id 0 Lun: 4
scsi0 Channel 00 Id 0 Lun: 5
---­---­---
uname -a shows the following afterr installing new kernel
Linux rac1 2.6.18-128.el5xen #1 SMP Wed Dec 17 12:22:24 EST 2008 i686
i686 i386 GNU/Linux




On Jan 22, 7:37 pm, chava45 ssch...@gmail.com wrote:
 Mike,
 iscsi: registered transport iscsi_tcp is not showing up in /var/log/
 messages and here is the output of tail -f /var/log/messages when the
 service iscsid start is executed
 /var/log/messages/ output
 ---­---­--
 Jan 22 19:24:24 rac1 iscsid: iSCSI logger with pid=4135 started!
 Jan 22 19:24:25 rac1 iscsid: transport class version 2.0-724. iscsid
 version 2.0-868
 Jan 22 19:24:25 rac1 iscsid: iSCSI daemon with pid=4136 started!
 Jan 22 19:24:27 rac1 iscsid: received iferror -38
 Jan 22 19:24:27 rac1 last message repeated 2 times
 Jan 22 19:24:27 rac1 iscsid: connection1:0 is operational after
 recovery (1 attempts)
 Jan 22 19:24:37 rac1 kernel: ping timeout of 5 secs expired, last rx
 4294947132, last ping 4294948382, now 4294949638
 Jan 22 19:24:37 rac1 kernel:  connection1:0: iscsi: detected conn
 error (1011)
 Jan 22 19:24:37 rac1 kernel: sd 0:0:0:0: SCSI error: return code =
 0x000e
 Jan 22 19:24:37 rac1 kernel: end_request: I/O error, dev sda

Re: iferror -38

2009-01-27 Thread chava45

Mike,
Here is the log information from /var/log/messages.

Jan 27 14:02:04 rac1 iscsid: iSCSI logger with pid=4380 started!
Jan 27 14:02:05 rac1 iscsid: transport class version 2.0-724. iscsid
version 2.0-868
Jan 27 14:02:05 rac1 iscsid: iSCSI daemon with pid=4381 started!
Jan 27 14:03:02 rac1 kernel: scsi1 : iSCSI Initiator over TCP/IP
Jan 27 14:03:03 rac1 kernel:   Vendor: OPNFILER  Model: VIRTUAL-
DISK  Rev: 0
Jan 27 14:03:03 rac1 kernel:   Type:   Direct-
Access  ANSI SCSI revision: 04
Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
sectors (537 MB)
Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
through
Jan 27 14:03:03 rac1 kernel: SCSI device sda: 1048576 512-byte hdwr
sectors (537 MB)
Jan 27 14:03:03 rac1 kernel: sda: Write Protect is off
Jan 27 14:03:03 rac1 kernel: SCSI device sda: drive cache: write
through
Jan 27 14:03:03 rac1 iscsid: received iferror -38
Jan 27 14:03:03 rac1 last message repeated 2 times
Jan 27 14:03:03 rac1 iscsid: connection2:0 is operational now
Jan 27 14:03:06 rac1 udevd-event[4401]: wait_for_sysfs: waiting for '/
sys/devices/platform/host1/session2/target1:0:0/1:0:0:0/ioerr_cnt'
failed
Jan 27 14:03:13 rac1 kernel:  sda:3ping timeout of 5 secs expired,
last rx 47558, last ping 48808, now 50058
Jan 27 14:03:13 rac1 kernel:  connection2:0: iscsi: detected conn
error (1011)
Jan 27 14:03:14 rac1 iscsid: Kernel reported iSCSI connection 2:0
error (1011) state (3)
Jan 27 14:03:16 rac1 iscsid: received iferror -38
Jan 27 14:03:16 rac1 last message repeated 2 times
Jan 27 14:03:16 rac1 iscsid: connection2:0 is operational after
recovery (1 attempts)
Jan 27 14:03:26 rac1 kernel: ping timeout of 5 secs expired, last rx
50814, last ping 52064, now 53314
Jan 27 14:03:26 rac1 kernel:  connection2:0: iscsi: detected conn
error (1011)
Jan 27 14:03:27 rac1 iscsid: Kernel reported iSCSI connection 2:0
error (1011) state (3)
Jan 27 14:03:29 rac1 iscsid: received iferror -38
Jan 27 14:03:29 rac1 last message repeated 2 times
Jan 27 14:03:29 rac1 iscsid: connection2:0 is operational after
recovery (1 attempts)
Jan 27 14:03:39 rac1 kernel: ping timeout of 5 secs expired, last rx
54071, last ping 55321, now 56571
Jan 27 14:03:39 rac1 kernel:  connection2:0: iscsi: detected conn
error (1011)
Jan 27 14:03:40 rac1 iscsid: Kernel reported iSCSI connection 2:0
error (1011) state (3)
Jan 27 14:03:42 rac1 iscsid: received iferror -38
Jan 27 14:03:42 rac1 last message repeated 2 times
Jan 27 14:03:42 rac1 iscsid: connection2:0 is operational after
recovery (1 attempts)
Jan 27 14:03:52 rac1 kernel: ping timeout of 5 secs expired, last rx
57327, last ping 58577, now 59827
Jan 27 14:03:52 rac1 kernel:  connection2:0: iscsi: detected conn
error (1011)
Jan 27 14:03:53 rac1 iscsid: Kernel reported iSCSI connection 2:0
error (1011) state (3)
Jan 27 14:03:55 rac1 iscsid: received iferror -38
Jan 27 14:03:55 rac1 last message repeated 2 times
Jan 27 14:03:55 rac1 iscsid: connection2:0 is operational after
recovery (1 attempts)
Jan 27 14:04:05 rac1 kernel: ping timeout of 5 secs expired, last rx
60583, last ping 61833, now 63083
Jan 27 14:04:05 rac1 kernel:  connection2:0: iscsi: detected conn
error (1011)
Jan 27 14:04:06 rac1 iscsid: Kernel reported iSCSI connection 2:0
error (1011) state (3)
Jan 27 14:04:08 rac1 iscsid: received iferror -38
Jan 27 14:04:08 rac1 last message repeated 2 times
Jan 27 14:04:08 rac1 iscsid: connection2:0 is operational after
recovery (1 attempts)
--
Thanks
Chava

On Jan 27, 10:33 am, Mike Christie micha...@cs.wisc.edu wrote:
 chava45 wrote:
  Mike,
  iscsi: registered transport iscsi_tcp is not showing up in /var/log/
  messages and here is the output of tail -f /var/log/messages when the
  service iscsid start is executed
  /var/log/messages/ output

 Is this in response to my question to try and make sure that we are
 starting up cleanly?

 So before you do service iscsi start, do a ps -u root | grep iscsid to
 make sure it is not running. If it is running do a serivce iscsi stop.

 Then do a ls /sys/class/iscsi_session to make sure everything is cleaned
 up. If it is not, stop here and give me the output of the ls command and
 do a ls /sys/class/iscsi_connection.

 Next, if there are not sessions running start iscsid by hand.

 # iscsid

 Then run iscsiadm to check out what targets are setup

 # iscsiadm -m node

 (you should see iqn.2006-01.com.openfiler:tsn.61b3375e9b1d)

 Then log in by hand:

 # iscsiadm -m node -T iqn.2006-01.com.openfiler:tsn.61b3375e9b1d -l

 Then send me the logs.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi

iferror -38

2009-01-15 Thread chava45

I have created two virtual machines with oracle VM which is Xen based
VM and installed openfiler 2.3 on one VM and Centos 5.2 on another VM
as iscsi client which has iscsi initiator.

the client could discover the target successfully with
iscsiadm -m discovery -t sendtargets -p IP address of the target

iscsiadm -m node -l gives the sucessful message

but I could not see any block devices in /dev. Instead of /dev/sda ,
it is showing as /dev/sga
i did
cat /proc/partitions and it is showing sda there. But in /dev/ it is
showing as /dev/sga, instead of ./dev/sda. So I am not able to partion
the /dev/sga as it says ' it is not a block device'

I checked the syslog with tail -f /var/log/messages and it has the
following error messages

rac2 iscsid: received iferror -38
rac2 last message repeated 2 times
rac2 iscsid: connection1: o is operational after recovery
rac2 kernel : ping timeout of 5 sec expired , last rx 825664 , last
ping 826914, now 828164
rac2 kerenl : connection 1:0:iscsi:detected conn error (1011)
rac2 kerenl: sd 0:0:0:2: SCSCI error : retrun code =0x0002
rac2 kernel: end_request : I/O error on dev sdc, logical block 0
rac2 kerenl : Buffere I/O error on device sda, logical block 0
rac2 kernel : Dev sdc: unnable to read RDB block 0
rac2 iscsid : kerenel reports ISCSI connection 1:0 error (1011) state
3

I stuckup here for weekes and not able to move forward. I need to
install Oracle rac on Oracle VM for testing with openfiler.
Any help is appreciated
I am very very thankful on this

Thanks
Chava
--~--~-~--~~~---~--~~
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 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: iferror -38

2009-01-15 Thread chava45

Mike,
Thank you for your fast response.
I have tried installing the following rpm
kernel-xen-2.6.18-128.el5.i686.rpm . But it did not help.
Do we need to do any additional things after installing that rpm?
i did
rpm -Uvh kernel-xen-2.6.18-128.el5.i686.rpm
on Cent 5.2
But it could not help.


Thanks
Chava

Mike Christie wrote:
 chava45 wrote:
  I have created two virtual machines with oracle VM which is Xen based
  VM and installed openfiler 2.3 on one VM and Centos 5.2 on another VM
  as iscsi client which has iscsi initiator.
 

 Is the 5.3 kernel out yet?

 If not could you try this kernel
 http://people.redhat.com/dzickus/el5/128.el5/
--~--~-~--~~~---~--~~
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 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---