kristof wrote: > If you have a mirrored iscsi zpool. It will NOT panic when 1 of the > submirrors is unavailable. > > zpool status will hang for some time, but after I thinkt 300 seconds it will > put the device on unavailable. > > The panic was the default in the past, And it only occurs if all devices are > unavailable. > > Since I think b77 there is a new zpool property: failemode, which you can set > to prevent a panic: > > failmode=wait | continue | panic > > Controls the system behavior in the event of catas- > trophic pool failure. This condition is typically a > result of a loss of connectivity to the underlying > storage device(s) or a failure of all devices within the > pool. The behavior of such an event is determined as > follows: > > wait Blocks all I/O access until the device con- > nectivity is recovered and the errors are > cleared. This is the default behavior. > > continue Returns EIO to any new write I/O requests > but allows reads to any of the remaining > healthy devices. Any write requests that > have yet to be committed to disk would be > blocked. > > panic Prints out a message to the console and gen- > erates a system crash dump. > > > This is encouraging, but one problem: Our system is on Solaris 10 U4. Will this guy be immune to panics when one side of the mirror goes down? Seriously, I'm tempted to upgrade this box to OS b8? However, there are a lot of dependencies which we need to worry about in doing that - for example, will all our off the shelf software run with Open Solaris. More things to test.
Thanks, Jon _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
