|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Friday 08 April 2005 03:21 pm, Mike Christie wrote:
Using 126.96.36.199, it works when Multipath=no. But setting Multipath=portal causes the same log problems I have with 4.0.2.
ah ok. Let me see. Is this the case for you too dom?
We haven't used multipath or portfailover options yet, and they're commented out in our config files. Unless they are used by default, then unfortunately no, it's not the same as our case.
In the older versions failover was on by default, so it may have looked like everything was ok, but you may have just not failed back to the paths that are sptting out the error messages below.
In the newer versions we do the equivalent of Multipath=yes PortalFailover=no
Setting Multipath to no and Portfailover to no explicitly unfortunately did not solve this issue.
It shouldn't. In 4.0.2 we only support Multipath=yes and PortalFailover=no.
If you try 188.8.131.52 or below and you set Multipath=yes PortalFailover=no
Does it work?
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-iscsi-users mailing list linux-iscsi-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/linux-iscsi-users
[IP Storage] [IETF] [Linux SCSI] [iSCSI Book] [Linux Resources] [Yosemite News] [Photo] [Home] [IETF Announcements] [IETF Discussion] [SCSI Hardware]