Hi, I have an S10U3 system with an iSCSI initiator that's supposed to be connected to and iSCSI target on another Sun box (runnin Nevada build 57).
Yesterday we had a number of power cuts, affecting both machines. Unfortunately the one with the target boots rather slowly. So my system boots up and says: Mar 14 16:24:00 foobar iscsi: [ID 286457 kern.notice] NOTICE: iscsi connection(5) unable to connect to target iqn.1986-03.com.sun:02:ca0776bd-2ce7-4771-82b0-e1d529b5059a (errno:146) As a result, my zpool goes offline. Now everything is back up again, how do I convince it to reactivate the connection? No amount of restarting the initiator or poking with devfsadm or format or cfgadm seems to do anything. The way I found was actually to run 'zpool status' which seemed to kick it just the right way so that the connection gets reestablished and I can then see the pool and the device in format. What it didn't do was remount the filesystems. OK, so I get in as root and run 'zfs mount -a'. This level of manual recovery is rather unsatisfactory. Is there a better way to make sure that the initiator reconnects cleanly even if the target isn't yet ready? -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
