[EMAIL PROTECTED] wrote on 10/07/2008 01:10:51 PM: > I don't know if this is already available in S10 10/08, but in > opensolaris build > 71 you can set the: > > zpool failmode property > > see: > http://opensolaris.org/os/community/arc/caselog/2007/567/ > > available options are: > > The property can be set to one of three options: "wait", "continue", > or "panic". > > The default behavior will be to "wait" for manual intervention before > allowing any further I/O attempts. Any I/O that was already queued would > remain in memory until the condition is resolved. This error condition can > be cleared by using the 'zpool clear' subcommand, which will attemptto resume > any queued I/Os. > > The "continue" mode returns EIO to any new write request but attempts to > satisfy reads. Any write I/Os that were already in-flight at the time > of the failure will be queued and maybe resumed using 'zpool clear'. > > Finally, the "panic" mode provides the existing behavior that was explained > above.
Huh? I was under the impression that this was for catastrophic write issues (no paths to storage at all) not just one side of a mirror being down? I run mostly zraid2 and have not tested mirror breakage but am I wrong in assuming that like any other mirroring system (hw or software) when you lose one side of a mirror for writes that the expected result is the filesystem stays online and error free while the disk(s) in question are marked as down/failed/offline? -Wade _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
