hmm, you mean that 865.9 can't understand this options in config or
why you recommend 865.15?
Also i saw this options in /etc/iscsi/nodes/reo.target/
192.168.1.10,3260,1/iface2
It is enough change this options only in iface2 file and reboot
machine?
--~--~-~--~~~---~-
Oh, and in this file too:
/etc/iscsi/send_targets/192.168.1.10,3260/~reo.target,
192.168.1.10,3260,1,iface3/iface3
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email
Well.
For now i made changes, and decide copy from reo to linux box
connected to it.
Well, looks better, but maybe it's same, bacause i found in logs then:
Apr 18 20:53:22 rat kernel: connection1:0: iscsi: detected conn error
(1011)
Apr 18 20:53:22 rat iscsid: Kernel reported iSCSI connection 1:0
On 22 апр, 19:30, Mike Christie <[EMAIL PROTECTED]> wrote:
> Is there anything in the target logs about an error at this time?
>
Hmm, i found something, but i'am not shure that it's correct log from
reo. May be it is, but just have wrong timestamp:
Mar 22 21:11:04.521 3040529328 INFO:iSCSI Logou
On 23 апр, 22:14, Mike Christie <[EMAIL PROTECTED]> wrote:
> I do not think the reo box likes obeys the immedate bit and probably
> thinks we should be incrementing the cmdsn.
>
> If you set
> node.conn[0].timeo.noop_out_interval = 0
> node.conn[0].timeo.noop_out_timeout = 0
>
> Does this help?
On 24 апр, 20:37, Mike Christie <[EMAIL PROTECTED]> wrote:
> Yes and no. The initiator can work fine without this setting, but it is
> a feature, so it does provide some benefit. If you are using multipath
> you want to set those values to non-zero, so we can detect errors in the
> network and fai
Oh, one more little question, i saw now intresting situation, before
my tests with this box, i mistakingly thinks that i have slow samba
that cause that, but when i start test, i saw intresting thing:
log into linux box, go to the folder where iscsi storage mounted, when
i try copy something from
