galego wrote:Would love love love to figure this out.
I'm sorry it wasn't straight forward to clear the errors here. You don't say what system you're running this on, but if it's a tower where it's trivial to swap drives (or if you want to temporarily partition your boot), or if you have another system available (including FreeBSD/Linux) you could try importing the pool elsewhere and attempting to clear the errors there maybe.
If it's truly annoying though and it's data that's important (not sure if "media server" means it's just a convenience storage for network movie access and the like or if it's used for important project media data) you could also treat this as an excuse to test you near-line replica with a nuke&pave onto a fresh pool. I recognize that could be a significant time sink (I've only got around 10TB but that's still the better part of a day to replicate) and it's galling to do use an inelegant brute force approach to what should be a simple quickie, I've just gone through a similar set of feelings with an obscure network hardware bug that I'd love to track down rather then just RMA the equipment. Still, it's not like it's a useless exercise on its own anyway. The old saw of "if you've never tested your backup you don't really have one" isn't without merit.
It's tough to expect much when I only interact in this forum when something is amiss. Although I suppose that paucity is a testament to the stability of OpenZFS on OS X.
That's likely a lot of it, but it probably also has to do with there being a great deal of time between stable releases, or even test releases for that matter (beyond "compile your own"), which slows down discussion a bit. At some point enough time goes by and you see enough fixes for various issues appearing in commits and developer discussion that it becomes unclear whether an issue is worth sinking a lot of time into diagnosis/testing because it may already be dealt with, and it's tempting to just wait for the next major and then see if the issue still exists.
O3X may also just lack critical mass right now, and Apple's regrettable decisions on the desktop computer front may have further reduced the most natural potential user base. I'd love to throw together a test pool to try to reproduce your problem for example but just am not really in a position to do it right now in terms of available systems, and I'm waiting on the the next release (maybe by the end of the year?) for two newer MPs so that I can try it with 10.12 as well.
I do also think that O3X is has made massive strides this year alone in terms of general production readiness. Features like Spotlight support are significant core issues for use under OS X (well, macOS now I guess, shucks I hadn't even considered how their rebrand messes with the lovely O3X acronym), so getting that sorted out was key. It sounds like this upcoming one will have native crypto (or at least make adding crypto easier) and significant numbers of QOL improvements, at which point I think it may well have 100% of the foundational stuff. From that other Sierra Disk Utility thread it sounds like there will even be an opportunity to start to have some simple GUI integration which would be pretty neat. Hopefully the future is reasonably bright.