Re: BUG: iscsid: Can not allocate memory for receive context.
Patch in this email merged in commit 36a8b41de43749d91dfd52f9c8ad4a454c9a8f15. On 07/29/2013 01:27 PM, Mike Christie wrote: Hi Julian, Thanks for the reply. Could you try the patch I posted? I attached it in this mail too. It should fix the recv context problem without having to modify the POOL MAX setting. On 07/18/2013 11:40 AM, Julian Freed wrote: Hi, you need to increase MAX in the source file open-iscsiversion/usr/initiator.h #define CONTEXT_POOL_MAX 32 Obviously you need to download sources and compile. It solves this problem. This problem happens when you have many devices or high loasd of io I use it in with ISCSI-SCST and still have other problems, when using many devices, and high io load On Saturday, July 6, 2013 6:34:08 PM UTC+3, myk...@gmail.com wrote: Exactly. I can log in but I do not see any LUNs. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: BUG: iscsid: Can not allocate memory for receive context.
On 08/02/2013 02:59 PM, Julian Freed wrote: Thanks for the patch. After few tests I believe it solves the problem, after restoring #define CONTEXT_POOL_MAX 32 Thanks for testing. Two more questions. I need to increase the lun_limit, currently it is limited to 511 I thought I found the limit in kernel/iscsi_tcp.c static unsigned int iscsi_max_lun = 512 But changing this, that did not help. Did you change the code or use the modparam that the code is for? What kernel is this with too? There is a weird kink with older kernels and that modparam. You had to set the param then do login. You also cannot write to the sysfs file. You had to do it modprobe time. The file in the kernel 3.8.4 seems to be unlimited static unsigned int iscsi_max_lun = ~0; By the way the file in the kernel is very different from open-iscsi-2.0-873 Yeah, the 512 limit in the old code was just a artificial limit. We used to hit bugs with older targets that would not respond to inquirys and report luns like how the scsi layer wanted it, so the scsi layer would drop down to sequential scans that took a long time. Those targets are longer really used and so the limit was removed in newer kernels. Another question: Why the iscsi login is so slow. It takes 40 seconds for 900 iscsi luns in 3 targets. Is the iscsi login slow or the device setup and discovery? When you run the iscsiadm login we do both. The iscsi login should be fast. Send the /var/log/messages so I can check. The device setup and discovery for 900 luns is probably slow. The scsi layer sends lots of commands to find luns and set them up. In newer kernels we do some of the setup in parrallel so that should help if your kernel has it on. It is still slow for 900 luns though. It seems you are used to looking at the source so if interested see sd_probe_async. The iscsi layer already does scsi scanning for each target async so ignore the scsi async scanning stuff. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG: iscsid: Can not allocate memory for receive context.
Thanks for the patch. After few tests I believe it solves the problem, after restoring #define CONTEXT_POOL_MAX 32 Two more questions. I need to increase the lun_limit, currently it is limited to 511 I thought I found the limit in kernel/iscsi_tcp.c static unsigned int iscsi_max_lun = 512 But changing this, that did not help. The file in the kernel 3.8.4 seems to be unlimited static unsigned int iscsi_max_lun = ~0; By the way the file in the kernel is very different from open-iscsi-2.0-873 Another question: Why the iscsi login is so slow. It takes 40 seconds for 900 iscsi luns in 3 targets. Thanks On Mon, Jul 29, 2013 at 9:27 PM, Mike Christie micha...@cs.wisc.edu wrote: Hi Julian, Thanks for the reply. Could you try the patch I posted? I attached it in this mail too. It should fix the recv context problem without having to modify the POOL MAX setting. On 07/18/2013 11:40 AM, Julian Freed wrote: Hi, you need to increase MAX in the source file open-iscsiversion/usr/initiator.h #define CONTEXT_POOL_MAX 32 Obviously you need to download sources and compile. It solves this problem. This problem happens when you have many devices or high loasd of io I use it in with ISCSI-SCST and still have other problems, when using many devices, and high io load On Saturday, July 6, 2013 6:34:08 PM UTC+3, myk...@gmail.com wrote: Exactly. I can log in but I do not see any LUNs. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG: iscsid: Can not allocate memory for receive context.
Hi Julian,
Thanks for the reply. Could you try the patch I posted? I attached it in
this mail too. It should fix the recv context problem without having to
modify the POOL MAX setting.
On 07/18/2013 11:40 AM, Julian Freed wrote:
Hi, you need to increase MAX in the source file
open-iscsiversion/usr/initiator.h #define CONTEXT_POOL_MAX 32
Obviously you need to download sources and compile.
It solves this problem.
This problem happens when you have many devices or high loasd of io
I use it in with ISCSI-SCST and still have other problems, when using
many devices, and high io load
On Saturday, July 6, 2013 6:34:08 PM UTC+3, myk...@gmail.com wrote:
Exactly. I can log in but I do not see any LUNs.
--
You received this message because you are subscribed to the Google
Groups open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send
an email to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.
diff --git a/usr/event_poll.c b/usr/event_poll.c
index f36fec1..939f1a2 100644
--- a/usr/event_poll.c
+++ b/usr/event_poll.c
@@ -165,8 +165,11 @@ void event_loop(struct iscsi_ipc *ipc, int control_fd, int
mgmt_ipc_fd)
exiting, res, errno);
break;
}
- } else
+ }
+
+ if (res = 0)
actor_poll();
+
reap_proc();
/*
* flush sysfs cache since kernel objs may
diff --git a/usr/netlink.c b/usr/netlink.c
index c07fe3c..754c3ea 100644
--- a/usr/netlink.c
+++ b/usr/netlink.c
@@ -1545,8 +1545,8 @@ static int ctldev_handle(void)
ev_context = ipc_ev_clbk-get_ev_context(conn, ev_size);
if (!ev_context) {
- /* retry later */
log_error(Can not allocate memory for receive context.);
+ drop_data(nlh);
return -ENOMEM;
}
Re: BUG: iscsid: Can not allocate memory for receive context.
Hi, you need to increase MAX in the source file open-iscsiversion/usr/initiator.h #define CONTEXT_POOL_MAX 32 Obviously you need to download sources and compile. It solves this problem. This problem happens when you have many devices or high loasd of io I use it in with ISCSI-SCST and still have other problems, when using many devices, and high io load On Saturday, July 6, 2013 6:34:08 PM UTC+3, myk...@gmail.com wrote: Exactly. I can log in but I do not see any LUNs. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: bug: iscsid: Can not allocate memory for receive context errors
On 07/07/2013 04:36 AM, myk...@gmail.com wrote:
6. Repeat volumes configuration this time configured 60 volumes
and map them. (Again to undefined initiators group)
Are you doing 60 volumes per target?
It looks like the target is flooding the initiator with reported luns
data changed async events from the above operations. From what I can
tell we are only supposed to get one per session. The initiator cannot
allocate resources to handle all the events and tries to retry later,
but that code just retries right away. We then get into a infinite loop.
The attached patch just drops the events when we get floods like these.
I would like to double check on the target analysis. If you have time do
a tcpdump/wireshark trace (no need for the logs), so we can see what the
target is sending us to make sure we can blame them :) I think I know
some extremeIO people so I can then bug them for a fix on their side too
(I will still merge the attached fix so we do not hang).
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.
diff --git a/usr/netlink.c b/usr/netlink.c
index c07fe3c..754c3ea 100644
--- a/usr/netlink.c
+++ b/usr/netlink.c
@@ -1545,8 +1545,8 @@ static int ctldev_handle(void)
ev_context = ipc_ev_clbk-get_ev_context(conn, ev_size);
if (!ev_context) {
- /* retry later */
log_error(Can not allocate memory for receive context.);
+ drop_data(nlh);
return -ENOMEM;
}
Re: bug: iscsid: Can not allocate memory for receive context errors
On 07/25/2013 02:31 AM, Mike Christie wrote: It looks like the target is flooding the initiator with reported luns data changed async events from the above operations. It actually might be from #6 or #7. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: bug: iscsid: Can not allocate memory for receive context errors
On 7/25/13 2:31 AM, Mike Christie wrote:
On 07/07/2013 04:36 AM, myk...@gmail.com wrote:
6. Repeat volumes configuration this time configured 60 volumes
and map them. (Again to undefined initiators group)
Are you doing 60 volumes per target?
It looks like the target is flooding the initiator with reported luns
data changed async events from the above operations. From what I can
tell we are only supposed to get one per session. The initiator cannot
allocate resources to handle all the events and tries to retry later,
but that code just retries right away. We then get into a infinite loop.
The attached patch just drops the events when we get floods like these.
The attached patch is better I think. It will try to run the queue after
we get a event so we should not get so backed up. We used to read in all
the events then try to run the queue.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.
diff --git a/usr/event_poll.c b/usr/event_poll.c
index f36fec1..939f1a2 100644
--- a/usr/event_poll.c
+++ b/usr/event_poll.c
@@ -165,8 +165,11 @@ void event_loop(struct iscsi_ipc *ipc, int control_fd, int
mgmt_ipc_fd)
exiting, res, errno);
break;
}
- } else
+ }
+
+ if (res = 0)
actor_poll();
+
reap_proc();
/*
* flush sysfs cache since kernel objs may
diff --git a/usr/netlink.c b/usr/netlink.c
index c07fe3c..754c3ea 100644
--- a/usr/netlink.c
+++ b/usr/netlink.c
@@ -1545,8 +1545,8 @@ static int ctldev_handle(void)
ev_context = ipc_ev_clbk-get_ev_context(conn, ev_size);
if (!ev_context) {
- /* retry later */
log_error(Can not allocate memory for receive context.);
+ drop_data(nlh);
return -ENOMEM;
}
Re: BUG: iscsid: Can not allocate memory for receive context.
Exactly. I can log in but I do not see any LUNs. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
BUG: iscsid: Can not allocate memory for receive context.
When running a load on top of CentOS 6.4 of mapping and unmapping of volumes, I'm getting the following errors: 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context (They quite flood the log actually). The flow: 1. Configured 50 volumes and map them to default initiator (Undefined) group 2. On th Client: multipath –F, rescan-scsi-bus –r, followed by multipath. 3. Removed all the volumes from the system. (And mappings) 4. Client: again- : multipath –F, rescan-scsi-bus –r, followed by multipath. 5. Repeat volumes configuration this time configured 60 volumes and map them. (Again to undefined initiators group) 6. Tried to rescan-scsi-bus –r again and got the flood from iscsid after which client is in distress (kill iscsid, rm of messages, reboot) [root@lg601 ~]# uname -a Linux lg601 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@lg601 ~]# rpm -qa |grep scsi iscsi-initiator-utils-6.2.0.873-2.el6.x86_64 lsscsi-0.23-2.el6.x86_64 Any ideas? TIA, Y. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
bug: iscsid: Can not allocate memory for receive context errors
On a fully updated CentOS 6.4, I'm seeing the following errors: 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. ... Installed packages: [root@lg601 ~]# uname -a Linux lg601 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@lg601 ~]# rpm -qa |grep scsi iscsi-initiator-utils-6.2.0.873-2.el6.x86_64 lsscsi-0.23-2.el6.x86_64 The test is more or less: 1. Configured 50 volumes and map them to default initiator (Undefined) group 2. Client: multipath –F, rescan-scsi-bus –r, followed by multipath. 3. At this point all is ok (so it seems) 4. Removed all the volumes from the system. (And mappings) 5. Client: again- : multipath –F, rescan-scsi-bus –r, followed by multipath. 6. Repeat volumes configuration this time configured 60 volumes and map them. (Again to undefined initiators group) 7. Tried to rescan-scsi-bus –r again and got the flood from iscsid after which client is in distress (kill iscsid, rm of messages, reboot) Any ideas? Thanks in advance, Yaniv. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: bug: iscsid: Can not allocate memory for receive context errors
On 07/02/2013 06:03 AM, myk...@gmail.com wrote: On a fully updated CentOS 6.4, I'm seeing the following errors: 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. ... Installed packages: [root@lg601 ~]# uname -a Linux lg601 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@lg601 ~]# rpm -qa |grep scsi iscsi-initiator-utils-6.2.0.873-2.el6.x86_64 lsscsi-0.23-2.el6.x86_64 The test is more or less: 1. Configured 50 volumes and map them to default initiator (Undefined) group 2. Client: multipath –F, rescan-scsi-bus –r, followed by multipath. 3. At this point all is ok (so it seems) 4. Removed all the volumes from the system. (And mappings) 5. Client: again- : multipath –F, rescan-scsi-bus –r, followed by multipath. 6. Repeat volumes configuration this time configured 60 volumes and map them. (Again to undefined initiators group) 7. Tried to rescan-scsi-bus –r again and got the flood from iscsid after which client is in distress (kill iscsid, rm of messages, reboot) I could not replicate this here. Could you run iscsid in debug mode? To do this do: 1. Stop all iscsi/iscsid services and logout of targets and shutdown iscsi multipath devices. 2. Run iscsid by hand # this will spit out lots of debug info to the screen. Redirect it to a file or capture from the screen. Whatever you prefer. iscsid -d 8 -f 3. Log in to your targets. iscsiadm -m node -l 4. Run your test. Send all the iscsid output. Also send the /var/log/messages. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG: iscsid: Can not allocate memory for receive context.
Hey, What target is this with? Some targets are going to allow different behavior when you remove/unmap volumes. On 07/02/2013 10:09 AM, myk...@gmail.com wrote: When running a load on top of CentOS 6.4 of mapping and unmapping of volumes, I'm getting the following errors: 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context (They quite flood the log actually). The flow: 1. Configured 50 volumes and map them to default initiator (Undefined) group 2. On th Client: multipath –F, rescan-scsi-bus –r, followed by multipath. 3. Removed all the volumes from the system. (And mappings) 4. Client: again- : multipath –F, rescan-scsi-bus –r, followed by multipath. 5. Repeat volumes configuration this time configured 60 volumes and map them. (Again to undefined initiators group) 6. Tried to rescan-scsi-bus –r again and got the flood from iscsid after which client is in distress (kill iscsid, rm of messages, reboot) [root@lg601 ~]# uname -a Linux lg601 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@lg601 ~]# rpm -qa |grep scsi iscsi-initiator-utils-6.2.0.873-2.el6.x86_64 lsscsi-0.23-2.el6.x86_64 Any ideas? TIA, Y. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG: iscsid: Can not allocate memory for receive context.
EMC's XtremIO (http://www.emc.com/storage/xtremio/index.htm). It's an All-Flash-Array (so quite fast) - perhaps it's relevant? Can you elaborate what do you mean by 'allow different behavior when you remove/unmap volumes' mean? Thanks, Y. On Tuesday, July 2, 2013 8:26:41 PM UTC+3, Mike Christie wrote: Hey, What target is this with? Some targets are going to allow different behavior when you remove/unmap volumes. On 07/02/2013 10:09 AM, myk...@gmail.com javascript: wrote: When running a load on top of CentOS 6.4 of mapping and unmapping of volumes, I'm getting the following errors: 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context. Jul 1 18:13:02 lg601 iscsid: Can not allocate memory for receive context (They quite flood the log actually). The flow: 1. Configured 50 volumes and map them to default initiator (Undefined) group 2. On th Client: multipath �F, rescan-scsi-bus �r, followed by multipath. 3. Removed all the volumes from the system. (And mappings) 4. Client: again- : multipath �F, rescan-scsi-bus �r, followed by multipath. 5. Repeat volumes configuration this time configured 60 volumes and map them. (Again to undefined initiators group) 6. Tried to rescan-scsi-bus �r again and got the flood from iscsid after which client is in distress (kill iscsid, rm of messages, reboot) [root@lg601 ~]# uname -a Linux lg601 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@lg601 ~]# rpm -qa |grep scsi iscsi-initiator-utils-6.2.0.873-2.el6.x86_64 lsscsi-0.23-2.el6.x86_64 Any ideas? TIA, Y. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+...@googlegroups.com javascript:. To post to this group, send email to open-...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
