I know this problem has been mentioned a while back, but I haven’t seen or found any usable solution. Sorry to bring it up again, especially if there IS a solution.
Problem: I have two servers: zeek and zed (both running nexenta flavor of Solaris x86). On zed I created a zpool using two SATA drives and exported them via iscsi. On zeek I created a zpool consisting of one local SATA drive + the iscsi partition from zed with the following command: # zpool create hybrid c0t5d0 c2t010000E0815E35D500002A0049313F80d0 the latter being the iscsi partition. It’s created fine, works fine, everything’s dandy... however: To test for fault tolerance, I downed the nic on zed (ifconfig bge0 down), and rebooted zeek. I was hoping that zeek would just alert me to zed not being available and finish booting. But no. Zeek just keeps on spitting out the following NOTICE messages: Notice: one or more i/o devices have been retired --- Notice: iscsi connection failed to set socket option TCP_NODELAY, SO_RCVBUF or SO_SNDBUF NOTICE: iscis connection(4) unable to connect to target SENDTARGETS_DISCOVERY NOTICE: iscsi discovery failure - SendTargets (192.168.001.102) --- over and over and over... until I up the nic card on (ifconfig bge0 up) Is there a way configure either ZFS or Solaris to ignore the pool called hybrid if zed cannot be reached, or time out after x number of trying to reach zed, or even mount just the local SATA disk only, or whatever it takes to simply booting up? Can’t believe the smart people behind ZFS overlooked this small detail. S.
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss