kristof wrote: > 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".
I'm fairly certain that this isn't what the OP was concerned about. The OP appeared to be concerned about ZFS's behaviour when one half of a mirror went away. As the pool is merely degraded, ZFS will continue to allow reads and writes... eventually... Depending on _how_ the disk is failing, I/O may become glacial, or freeze entirely for several minutes before recovering, or hiccup briefly and then go on normally. ZFS is layered to the point where stacked timeouts _may_ become unreasonably large (see many previous threads). And a single "slow" device will drag the rest of the volume with it (e.g. a disk that demands 10 retries per write). SVM suffers from some of the same problems, although not (in my experience) to the same degree. SVM tends to err on the side of "fail the disk quickly", whereas ZFS tries very very hard to make all I/O succeed, and relies on the fault management system or I/O stack to decide to fail things. -- Carson _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
