On 24 May 2010 at 9:06, 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/
block/sd#/device/timeout from 30 to a higher number, like 360, seems
to have improved
On 24 May 2010 at 16:15, Mike Christie wrote:
May 19 17:14:37 172.21.55.20 kernel: [615921.356701] connection21:0:
detected conn error (1020)
Hi,
would there be negative consequences when changing the name
connection21:0 to something more readable like connection-21:0 or
conn-21:0. I
Taylor wrote:
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?
We use PS6000 with 4x1G
I am using a Suse 11.0 kernel, with open-iscsi 2.0.870-26, and when we
contacted equallogic
Mike Christie wrote:
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:
Yeah, and netstat -in does show a few RX-ERR on the two 10 Gig NICs we
are connecting to the iSCSI san with.
So I don't know if thats because of the extremely high IO load. i.e.,
iostat is reporting 600,000 Kbytes/sec in writes across 4 LUNs during
our heavy testing.
--
You received this
Hi,
I have installed iscsi-initiator-utils for RHEL5 .
Here are the files which were made available :
rpm -ql iscsi-initiator-utils :
/etc/iscsi/iscsid.conf
/etc/rc.d/init.d/iscsi
/etc/rc.d/init.d/iscsid
/sbin/iscsi-iname
/sbin/iscsiadm
/sbin/iscsid
/sbin/iscsistart
On 05/24/2010 11:22 PM, Taylor wrote:
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
Ok, will find out about the equallogic setting. So if we are using
dm-multipath, we should not set those noop values to 0, but possibly
increase them for high IO loads?
On Tue, May 25, 2010 at 2:47 PM, Mike Christie micha...@cs.wisc.edu wrote:
On 05/24/2010 11:22 PM, Taylor wrote:
Yes, when I
The settings I see in iscsiadm seem fine.
On 05/25/2010 03:40 AM, 立凡 王 wrote:
May 25 11:18:33 milk kernel: connection2:0: ping timeout of 5 secs
expired, recv timeout 5, last rx 1457759, last ping 1462759, now
1467759
May 25 11:18:33 milk kernel: connection2:0: detected conn error (1011)
May 25
Sorry for the delay. I am almost done. Should have some comments later
tonight.
Did you have a patch to modify cxgb3i?
On 05/15/2010 12:24 PM, Rakesh Ranjan wrote:
The following 3 patches add a new iscsi LLD driver cxgb4i to enable iscsi
offload
support on Chelsio's new 1G and 10G cards.
On 05/26/2010 01:53 AM, Mike Christie wrote:
Sorry for the delay. I am almost done. Should have some comments later
tonight.
Did you have a patch to modify cxgb3i?
Hi Mike,
We are doing cxgb3i patch and will submit by this weekend.
Regards
Rakesh Ranjan
On 05/15/2010 12:24 PM, Rakesh
On 05/25/2010 04:15 PM, Taylor wrote:
So far blowing away SUSE 11 and installing OpenSuse has resolved the
Just so you know , the SUSE developers are good at keeping SLES up to
date and even have fixes that are not yet upstream, so it is sometimes
best to just get their newest SLES kernels.
Thanks for the suggestions, I did change the io scheduler to make sure
it was same as other server we were testing on.
Not using iptables, and cpu frequency scaling or whatever its called
is not enabled.
To us this looks like an issue with worse network performance with later
kernels. The kernel
On 05/25/2010 08:04 PM, Mike Christie wrote:
On 05/19/2010 05:17 PM, Anton Altaparmakov wrote:
Is there anyway you can give me the libiscsi.c, iscsi_tcp.c and if it
exists the libiscsi_tcp.c files for kernel that worked and did not work?
Sure, attached... The sp2-iscsi directory is the
On 05/19/2010 05:17 PM, Anton Altaparmakov wrote:
Not sure about ethereal. Would tcpdump do? What options would you like me to
run it with?
If using tcpdump is easier than trying to use the old modules on the new
kernel then do that. Maybe we will have to do both to rule out the iscsi
15 matches
Mail list logo
