Consider adding warnings against using ZFS native encryption

The 80% "rule" hasn't been a thing for a while, but any filesystem is going to have issues with finding free blocks as it fills up...

Ext used to reserve 3-5% "for root", but the reality is that you're supposed to free up space if you let it get that full.

Because ZFS has one of the most robust RAID systems in an opensource filesystem, and is incredibly mature.

And to be fair, almost every file system will have degraded performance and increased fragmentation above 80/90% full, so this should be considered universal advice.

There is also a legitimate question of how wide spread the issues are with the ZFS encryption feature. The fact this hasn't picked up much steam implies its not a common issue.

this will be a cool bug to check in on. its already fun to click on bugs or issues related to encryption / send combos with someone even getting results like spilling unencrypted data straight to disk haha theres so many links in the "this issue is referenced by" sort of thing, it becomes like a maze. I obviously can't tell whether the de-encryption of sensitive data is because of confusion on the end users part because the only thing I know about zfs send was that my boss couldn't get it to work and his vendor said our installation was not supported. I think our OS was something like that openindiana / illuminos or whatever haha

best comment that summarizes the issue for me at least:

"I personally am just treating the native encryption code as unmaintained at this point, though, and would advise most other people do the same."