@ToshInMacc What was the typo? What OpenZFS document mentions the absolute need for minimum of 4 disks?
For #RAIDZ2 #OpenZFS documentation mentions https://openzfs.github.io/openzfs-docs/Basic%20Concepts/VDEVs.html#what-are-the-different-types-of-vdevs ...
『... Requires at least 3 disks (5+ recommended), can tolerate two drive failures.』
The recording of the March 18th, 2026 #OpenZFS Production User Call is up:
We discussed debz, a ZFS-based system deployment and orchestration platform, #CachyOS, ZFSBootMenu, recovering a single file from a ZVOL, and more! (Pardon the poor quality audio while I was on the road. It got better!)
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
#OpenZFS no longer warns you when you create a pool with mismatched VDEVs, e.g.:
# zpool create daft raidz s2d0-WD-08NRX3 s2d1-NCC-1701D s2d2-TOSH-9268 s2d3-SEA-4N0M7 mirror s2d4-SAN-XL905 s2d5-GOOG-4C02
Once upon a time, you needed to use -f to force this. I wonder why this is allowed? Seems unnecessarily risky. Once upon a time, such pools were full-on unrepairable.
The recording of the March 11th, 2026 #OpenZFS Production User Call is up:
We discussed the bale snapshot viewer, Linux kernel compatibility documentation, upcoming mount point improvements, OpenZFS hardware acceleration, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
Part 2 of the FreeBSD Foundationals series is out! "ZFS - The Last Filesystem You'll Ever Need."
We go from the philosophy of silent data corruption to practical, battle-tested data management. Covers pools, datasets, why you shouldn't blindly add L2ARC, native encryption, and using sanoid/syncoid to turn backups into a solved problem.
If you've ever lost data and decided "never again," this is for you. 
https://blog.hofstede.it/freebsd-foundationals-zfs-the-last-filesystem-youll-ever-need/
🪤 TrueNAS Deprecates Public Build Repository and Raises Transparency Concerns
｢ Public build systems allow community members to inspect and reproduce the steps used to generate official releases. When those pipelines run behind internal infrastructure, it becomes harder for external contributors to verify that the released binaries match the public source code exactly ｣
https://linuxiac.com/truenas-moves-build-system-internal/
@mrmasterkeyboard @xinit the #RightToFork is elemental to #FLOSS and necessary for #OpenSource to exist.
We ain't criticizing corporations that maintain outdated inhouse forks out of principle, and I think that #evi isn't a "fork for the sake of forking" but actually does things different and apparenty "irreconcileable" to the mainline Project.
Nit to mention EVERYTHING IS "#POLITICAL" - including "apoliticalness"!
FreeBSD 14.4-RELEASE is out — the fifth release on the 14-STABLE branch.
Highlights:
- OpenSSH 10.0p2 — post-quantum key exchange by default, DSA dropped, sshd-auth split out
- OpenSSL 3.0.16
- OpenZFS 2.2.9
- New sndctl(8) utility for sound devices
- Two jail escape vulnerabilities patched
- Raspberry Pi Zero 2W now supported
Full breakdown: https://www.opensourcefeed.org/freebsd-14-4-released/
#OpenZFS now has much more detailed information about which varieties of Linux are supported.
tl;dr: all kernel.org "longterm" series, all RHEL active & maintenance series (including clones), and Ubuntu LTS.
(No actual change in practice, just trying to write it down a bit more clearly).
https://github.com/openzfs/zfs/?tab=readme-ov-file#supported-kernels-and-distributions
Shawn Webb
ax6761
Michael Dexter
Michael W Lucas 
Larvitz 
jbz
Kevin Karhan 
opensourcefeed
Rob 💚