This has nothing to do with ZFS. It has everything to do with the way Solaris manages
faults, with its default settings. AFAIK, Nexenta does not change these defaults, so they
are similarly affected. Clearly, OSX is not Solaris and therefore must have a different
mechanism for declaring a retirement.
That said, in my ZFS tutorials, I go through some analysis that explains how you can
determine whether hot spares are worthwhile. In general, more parity is better than
less parity + spares. Intuitively, this makes sense if you think of a hot spare as an
unsilvered parity disk... if you keep it silvered, you don't have to resilver it after a
failure. This intuition works for smallish deployments, but you'll need to do some math
for configs with more than a few dozen disks.
The other angle is that for sites providing 7x24 support, hot spares don't offer much value.
Hot spares are great for sites where the staff goes home over the weekend.
-- richard