Hi,
After a little more experimenting, I think this iscsi-targets fault.
I agree this does not have any relevance to the open-iscsi code,
nevertheless, I though it would nice to post here as well to keep this
post updated. Do apologize if that is against the principles of this
mailing-list.
In thinking further about this, the application pool could scale up to
40 TB. Is a 40 TB volume out of reality?
On May 21, 11:51 am, Terry [EMAIL PROTECTED] wrote:
Hello,
I am going to be connecting to an equallogic san using RHEL5 x86_64
and serving up NFS volumes. I don't have any
Hi Tomasz (or maybe other who can help ??)
could you compile openiscsi for a self-compiled xen ?
Could your please so kind and tell me,
how to modify the xen-source-directory structure and/or
the openiscsi-source-directory structure (copy/move/edit) to build
openiscsi from scratch.
For compile
On Wed, May 21, 2008 at 10:18:22AM -0700, Terry wrote:
In thinking further about this, the application pool could scale up to
40 TB. Is a 40 TB volume out of reality?
On May 21, 11:51 am, Terry [EMAIL PROTECTED] wrote:
Hello,
I am going to be connecting to an equallogic san using
HIMANSHU wrote:
Yeah..I am using IET.
I was getting session recovery timed out after 120 secs when it was
120.
Now as it is 86400,I never observed after 86400sec. that
session recovery timed out after 86400 secs.
Otherwise is it NORMAL behavior of IET that the connection is lost of
I go this message wihle compiling 869.2
I didn't had problem with previous kernel
version 865.4 865.8 865.12 865.15 have the same result
Any ideas ?
node1:/download/open-iscsi-2.0-869.2 # uname -a
Linux node1 2.6.16.60-0.23-xen #1 SMP Thu May 15 06:38:31 UTC 2008
x86_64 x86_64 x86_64
hg wrote:
I go this message wihle compiling 869.2
I didn't had problem with previous kernel
version 865.4 865.8 865.12 865.15 have the same result
Any ideas ?
I think you need the attached patch. I have not merged it because it
ends up breaking other builds. We need someone with some
Please review our new version of the iSCSI drivers for Broadcom BNX2
devices. We've reworked the bnx2i driver quite a bit with the help
of Mike Christie in the last few months. It is now one scsi host per
adapter and has a single iscsi transport name. It is also more
tightly coupled to
Add interface for a separate CNIC driver to drive additional rings
and other resources for iSCSI.
A probe function is exported so that the CNIC driver can get
information about bnx2 devices. After calling the probe function,
the CNIC driver can then register with the BNX2 driver before
