Since we’re on the topic if encryption, there’s an elephant in the room I’d like to bring up that some don’t know may be there.
Currently, the implementation of encryption in ZFS has multiple unresolved edge case bugs, which can cause kernel panics, pool corruption or even pool destruction not just in the home pool, but in ones that receive a send as well apparently. Usually ZFS bugs are remarkably safe in regards to data, but not this time.
I don’t personally use native encryption yet, and had kinda forgotten the issues (and the very disappointing dev response) but this thread thankfully reminded me.
Here is a doc created and maintained by Rincebrain that gives a good summary of the reported issues and their status. Apparently it needs to be updated again: OpenZFS open encryption bugs (public RO) - Google Drive
And here is how to easily see all the open encryption related issues on github: Issues · openzfs/zfs · GitHub
Basically I highly recommend looking through the bugs to if what you want to do looks like one of those.
The data hazard is mitigated by not using send/recv of encrypted pools, and instead using rsync or something similar to replicate data for the time being. Personally, I’d stick with LUKs on a server if I wanted encryption for now. Not ideal, but time tested and stable.
I’ll repeat this post in my ZFS update thread later so more people are exposed to it hopefully.