ok it worked after a reboot.but dropping eid does not make sense to me.
What might be the exact cause of this eid being the FQDN not to be
authorised???
On Tue, Jan 13, 2009 at 11:27 PM, Nikhil nikhil.talpalli...@gmail.comwrote:
Hi,
It does not work for me :(
I used target name instead
HIMANSHU schrieb:
IET target is connected by MS initiator.Data transfer is going on on
the connected disk on initiator.
I don't see how your question fits here - you use IET as a target, and a
MS initiator.
This is open-iscsi (initiator) list, not a general
iSCSI-related-questions list.
IET target is connected by MS initiator.Data transfer is going on on
the connected disk on initiator.
TCP connection failed(because of any reason,service failure,problems
in kernel modules) at say 't1' second.Initiator kept trying for
reconnect.
Initiator actually recognizes that target is
On 14 Jan 2009 at 4:25, HIMANSHU wrote:
IET target is connected by MS initiator.Data transfer is going on on
the connected disk on initiator.
TCP connection failed(because of any reason,service failure,problems
in kernel modules) at say 't1' second.Initiator kept trying for
reconnect.
On Thu, 2009-01-08 at 15:06 -0600, Mike Christie wrote:
Karen Xie wrote:
[PATCH] iscsi_tcp - make padbuf non-static
From: Karen Xie k...@chelsio.com
virt_to_page() call should not be used on kernel text and data addresses.
virt_to_page() is used by sg_init_one(). So change padbuf
Boaz Harrosh wrote:
Remove the dark ages /* define debug_print */ in code, to use
a Kconfig option. With a system like Kconfig, in code, commented out,
configuration options are slavery and hard work.
(version control, manual edit ... need I say more)
I've used an int config bit-mask so
Hello all,
I tried a simple test:
1. Installed an iSCSI target. I tried this with both IET
(iscsitarget.sourceforge.net) and tgt (apt-get install tgt).
2. Created a 2GB file to use as the target.
3. Connected to the target with iscsiadm.
4. Ran the following command to test read throughput: dd
On Mon, Jan 12, 2009 at 11:48 AM, avis...@gmail.com wrote:
Here are some statistics from wireshark:
Bad checksum(TCP): 35,963
Usually this means that Wireshark was unable to capture all packets,
not that there was a problem with the packets themselves.
Bart.
Hi,
The iSNS server refuses connection to a network entity (eid) if there exists
an object already registered with the same network entity id but different
iSCSI node type(i.e. one initator and other target or vice versa). But if
the iSCSI node type is same (in case of two targets on same network