Hi Bob, Sorry I have not had a lot of spare time lately...
So the LSI-sourced arrays have bits in the inquiry data that tells the host whether or not the path that the inquiry is being handled on is a preferred or secondary path... When a path is brought online (or back online after going away), MPxIO is supposed to use that information to know whether or not to attempt to failback the LUN or not.. If you can collect the support data via CAM, I can take a look at your configuration...but basically it will likely come down to: 1) If the preferred owner of a LUN is not what you expected...which I assume you checked already... 2) A timing issue that is either causing the controller to not set the correct bit during re-discovery or 3) A timing or load related issue that is causing the host to "drop the ball" during re-discovery BTW, The Wide-port message you see when you reset a controller is likely the surviving controller noticing that it lost one of its back-end SAS channels until the other controller comes back... -Joel -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
