Rob Norris

Yeah, you're right. Unfortunately, right now it's a fairly common pattern within OpenZFS to just panic when something strange happens, which in kernel context, takes the whole kernel down. The...

Pretty much this. I'm personally interested in this sort of work, because it usually makes things generally more robust, beyond just the panic points. If nothing else, because a whole...

Two thoughts: - maybe a skip if you don't have `mkfs.xfs` and/or XFS support in your kernel (I routinely don't have those in my tiny VMs) - it's more work,...

Is there a clear thing that this solves on its own? I'm not saying there's not, but `free_inode` was introduced in torvalds/linux@fdb0da89f4ba for the 5.2 series, and I don't see...

@snajpa thanks. I wasn't sure; there's a few different things mentioned in that PR.

If it helps, here's a branch I was working on last year trying to do roughly the same thing: https://github.com/robn/zfs/commits/byte-prefix/. Please feel free to steal from it, at least the...

I guess mostly I don't see what the actual gain is. IME "standards compliance" is rarely by itself a good reason to do anything. If we were starting from scratch,...

> It might not look great, but it is done that way intentionally. If we are writing several copies of a block to a several different top-level vdevs, we want...

Rebased, and updated to move the unthrottle back to when the top vdev IO finishes. `resilver_restart_002` still fails, pretty sure it'll be something around about where errors are being accounted...

> `resilver_restart_002` still fails, pretty sure it'll be something around about where errors are being accounted to. I'll get back to it properly next week. Sorta-kinda. It was actually around...