Adjusting node.conn[0].timeo.noop_out_interval and
node.conn[0].timeo.noop_out_timeout to 0
didn't seem to make a difference. But increasing the value of /sys/
block/sd#/device/timeout from 30 to a higher number, like 360, seems
to have improved things...
Is that something you would expect? Do
Hi,
i'm running open-iscsi 2.0.871 userspace tools and modules from kernel
2.6.33.3.
I encounter a strange problem sometimes when I connect using multipath
to an equallogic
array.
I have interfaces eth1 and eth3 in the ISCSI network and if I connect
to a target on the equallogic
array it
Hey so with Win7 you get around 10 MB/s and when you do reads to the
iscsi disk /dev/sdb directly you got 9.5 MB/s, but when writing to the
disk you get around 1 MB/s, right?
YES
These are the dd testing outcome.
# dd if=/dev/zero of=/dev/sdc bs=1M count=1024
1024+0 records in
1024+0 records
We are having similar problems. (More connection failed and ping
timeouts as opposed to Authentication/login issues) Is your equallogic
array 1Gig or 10 Gig?
I am using a Suse 11.0 kernel, with open-iscsi 2.0.870-26, and when we
contacted equallogic (dell) they said the logs show the array isn't
Are you using ifaces to bind sessions to eth3?
On 05/22/2010 04:12 AM, pli wrote:
In syslog I find the following:
May 19 17:14:37 172.21.55.20 kernel: [615921.348161] scsi21 : iSCSI
Initiator over TCP/IP
May 19 17:14:37 172.21.55.20 kernel: [615921.356701] connection21:0:
detected conn error
Hi Mike,
I don't have a version of brcm_iscsiuio which I have readily avaliable
for 5.5.z which has the fix you are looking for without adding new
features. I will need to create a version of brcm_iscsiuio with the
iscsid/brcm_iscsiuio backported for 5.5.z. When does this need to be
On 05/23/2010 10:47 PM, 立凡 王 wrote:
Hey so with Win7 you get around 10 MB/s and when you do reads to the
iscsi disk /dev/sdb directly you got 9.5 MB/s, but when writing to the
disk you get around 1 MB/s, right?
YES
These are the dd testing outcome.
# dd if=/dev/zero of=/dev/sdc bs=1M
On 05/24/2010 11:06 AM, Taylor wrote:
Adjusting node.conn[0].timeo.noop_out_interval and
node.conn[0].timeo.noop_out_timeout to 0
didn't seem to make a difference. But increasing the value of /sys/
If it did not make a difference then it might not have got set right. If
you set them to 0,
Mike and all, okay, noted about the ping timeout messages. I set both
of
those values by running:
iscsiadm --mode node --o update -n
node.conn[0].timeo.noop_out_interval -v 10
iscsiadm --mode node --o update -n node.conn[0].timeo.noop_out_timeout
-v 10
I verifed the settings took via iscsiadm
Yes, when I get to office tomorrow I can attach screen output of make
fail, as well as support info with equallogic.
I guess to a different point, I understand if we are just killing the
disk that can cause problems, but how can I set it up so that IO is
slow or queues, and doesn't cause
10 matches
Mail list logo
