Tomasz Chmielewski wrote:
Mike Christie schrieb:
The scsi layer sets a timeout on each command. If it does not execute in
X seconds, it will run the iscsi eh.
So you can increase the scsi command time:
To modify the udev rule open /etc/udev/rules.d/50-udev.rules, and find the
following
Mike Christie schrieb:
The scsi layer sets a timeout on each command. If it does not execute in
X seconds, it will run the iscsi eh.
So you can increase the scsi command time:
To modify the udev rule open /etc/udev/rules.d/50-udev.rules, and find the
following lines:
ACTION==add,
On Thu, Jan 8, 2009 at 12:44 PM, Tomasz Chmielewski man...@wpkg.org wrote:
Anyone using iSCSI over DRBD? And a slow internet link perhaps?
How reliable is the link you are using -- which percentage of packets
is lost ? You can test this e.g. with the ping command. The following
command will
On Fri, Jan 9, 2009 at 3:22 PM, Tomasz Chmielewski man...@wpkg.org wrote:
Bart Van Assche schrieb:
# ping -q -i 0.01 -c1000 -s160 ${remote_ip}
I get about 1% losses.
IMHO running iSCSI over a slow link should work, but a packet loss of
1% is troublesome. On a local network the packet loss
Bart Van Assche schrieb:
On Fri, Jan 9, 2009 at 3:22 PM, Tomasz Chmielewski man...@wpkg.org wrote:
Bart Van Assche schrieb:
# ping -q -i 0.01 -c1000 -s160 ${remote_ip}
I get about 1% losses.
IMHO running iSCSI over a slow link should work, but a packet loss of
1% is troublesome. On a
Anyone using iSCSI over DRBD? And a slow internet link perhaps?
If yes, you are likely to see connection errors, host resets, and eventually,
I/O errors reported, for example:
Jan 7 21:47:09 vmware1 kernel: connection23:0: iscsi: detected conn error
(1011)
Jan 7 21:47:10 vmware1 kernel:
Tomasz Chmielewski wrote:
Anyone using iSCSI over DRBD? And a slow internet link perhaps?
If yes, you are likely to see connection errors, host resets, and eventually,
I/O errors reported, for example:
Jan 7 21:47:09 vmware1 kernel: connection23:0: iscsi: detected conn error
(1011)
