On Fri, 2010-05-14 at 11:46 -0500, Mike Christie wrote: > > We had some issues with the initiator loosing connections with the > > target in this new Karmic rootfs on iSCSI setup. The problem is > that > > after some time the filesystem switches to a read-only mount > following > > I/O errors after some activity on the initiator. > > Do you have the log messages for that? Did you see any ping/nop > timeout > messages (for root on iscsi set node.conn[0].timeo.noop_out_interval > and > node.conn[0].timeo.noop_out_timeout to 0).
The logs have rolled over since the event unfortunately (just checked). The output was minimalistic; two lines a few times.. and I recall a generic timeout message. I think this is exactly what it was, but no way to verify. Unfortunately I don't want to change DNS again simply to cause the problem. It has been stable since I made the DNS change, and runs some fairly important things that won't be migrated for some time. I have additionally disabled the alb load balancing pending a migration to true 802.11ab+ad link aggregation at the switch, further distancing myself from being able to retest this scenario with the possibly related poor-man's channel bonding enabled. cheers, Ian -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
