Not sure how this is supposed to work. Found as part of OpenStack testing,
but I don't think it's relevant:
[root@lgdrm1110 cinder]# ping6 fd00:206:553::7
PING fd00:206:553::7(fd00:206:553::7) 56 data bytes
64 bytes from fd00:206:553::7: icmp_seq=1 ttl=64 time=0.213 ms
64 bytes from fd00:206:5
Answer to self (sorry, could not find it anywhere but a friend reminded it
to me):
Use '[ ]' , for example:
[root@lgdrm1109 ~]# iscsiadm -m discovery -t sendtargets -p
[fd00:206:553::7]:3260
[fd00:206:553::3]:3260,1 iqn.2008-05.com.xtremio:001e679fa196
[fd00:205:553::3]:3260,1 iqn.2008-05.com.x
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
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
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, se
