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
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
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 =
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
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
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
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
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
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,
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
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
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:
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
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
14 matches
Mail list logo
