Hey,
At storage summit this year, it was decided iscsi needs to catch up with
the other iscsi drivers, and add something like FC's dev_loss_tmo. When
this timeout expires, it will cause the iscsi layer to remove the scsi
devices and fail any IO that was queued. Upper layers like dm-multipath
Some random comments:
1) What will be the default value for the new timeout?
2) I think this should be at least KERN_WARN(ing):
+ iscsi_cls_session_printk(KERN_INFO, session,
+session dev loss timed out after %d secs\n,
+
On 10/06/2010 04:54 AM, Ulrich Windl wrote:
Some random comments:
1) What will be the default value for the new timeout?
Not, sure yet. Suggestions?
2) I think this should be at least KERN_WARN(ing):
+ iscsi_cls_session_printk(KERN_INFO, session,
+
Hi all,
I have a server with two NICs on the same subnet. How can I force
iSCSI traffic to only use one of these?
I see the readme states you can use interface files in /etc/iscsi/
interfaces. So for example scenario I have these two NICS as below.
NIC1
IP address: 192.168.2.2
MAC:
Hi All!
I'm currently trying connect to a LaCie Ethernet Disk Raid using iSCSI. I'm
perfectly aware of the fact, that it isn't officially supported, however there
is a Backup Utility for Windows which uses the Microsoft iSCSI Initiator (and
adds a new Portal / Target there).
I already managed
On 10/06/2010 10:22 AM, jimmy wrote:
Hi all,
I have a server with two NICs on the same subnet. How can I force
iSCSI traffic to only use one of these?
I see the readme states you can use interface files in /etc/iscsi/
interfaces. So for example scenario I have these two NICS as below.
NIC1
IP
On 10/06/2010 04:09 AM, Koller Wolfgang wrote:
Hi All!
I'm currently trying connect to a LaCie Ethernet Disk Raid using iSCSI. I'm
perfectly aware of the fact, that it isn't officially supported, however there
is a Backup Utility for Windows which uses the Microsoft iSCSI Initiator (and
adds
