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 18:1
This fixes a problem where a host which is inaccessible would block the
scan of other hosts in the system.
Signed-off-by: Saggi Mizrahi
---
usr/iscsi_sysfs.c | 57 +--
usr/iscsi_sysfs.h | 3 ++-
usr/iscsiadm.c| 18 ++
3 fil
On Jun 27, 2013, at 2:57 PM, Or Gerlitz wrote:
> On Thu, Jun 27, 2013 at 7:25 PM, Mike Christie wrote:
>>
>> On 06/27/2013 08:46 AM, Or Gerlitz wrote:
>>> @@ -501,6 +503,18 @@ iscsi_iser_set_param(struct iscsi_cls_conn
>>> *cls_conn,
>>> return -EPROTO;
>>> }
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 isc
Hey,
Is it easy for you to replicate this problem and if so would it be
possible to run with a patch that spits out some extra debugging info?
It is easy for me to replicate with the Oracle linux kernel, but when I
add debugging it seems to move around or become difficult to hit.
On 06/27/2013
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 lg60
Hi Mike,
For us it happened only once till now; and from our kernel log, I don't
think anything special was going on during that time, except that we were
reading the sysfs entry. Can you pls share how do you replicate the problem
with the Oracle kernel? If this narrows us down a bit on how to
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
On Tue, Jul 2, 2013 at 6:45 PM, Michael Christie wrote:
>
> On Jun 27, 2013, at 2:57 PM, Or Gerlitz wrote:
>
>> On Thu, Jun 27, 2013 at 7:25 PM, Mike Christie wrote:
>>>
>>> On 06/27/2013 08:46 AM, Or Gerlitz wrote:
@@ -501,6 +503,18 @@ iscsi_iser_set_param(struct iscsi_cls_conn
*cls_c
On 07/02/2013 02:21 PM, myk...@gmail.com wrote:
> 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?
When you unmap
11 matches
Mail list logo