On 07/02/2013 02:21 PM, [email protected] 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 a volume with your target what does it do basically? Will
it allow you to login (create a iscsi session) at least? Does it allow
you to login but not show any luns?



> 
> 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, [email protected] <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 [email protected] <javascript:>.
>     > To post to this group, send email to [email protected]
>     <javascript:>.
>     > Visit this group at http://groups.google.com/group/open-iscsi
>     <http://groups.google.com/group/open-iscsi>.
>     > For more options, visit https://groups.google.com/groups/opt_out
>     <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 [email protected].
> To post to this group, send email to [email protected].
> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to