The OpenZFS project has shipped version 2.4.2, a maintenance release that pushes kernel compatibility forward to the Linux 7.1 series while addressing a stack of corruption bugs and rebuild edge cases. The release supports Linux kernels from 4.18 through 7.0 (with 7.1 patches landed in this version) and FreeBSD 13.3+ and 14.0+, keeping the cross-platform filesystem viable across the range of distributions and BSD releases currently in production.
The most consequential fixes target dRAID, the declustered RAID variant used in larger storage deployments. The release resolves rare checksum errors after rebuilds (#18473), data corruption following a disk clear (#18294, checksum errors after rebuilds with degraded disks (#18414), and import failures after disk replacements (#18380). A separate fix permits sequential resilver reads from degraded vdevs (#18405), and a deadlock in dmu_tx_assign() triggered by vdev_rebuild() has been cleared (#18258).
On the Linux side, the developers continued the substantial work of porting OpenZFS to the new fs_context-based mount API, which is now mandatory on recent kernels. A series of patches under #18377 and #18339 rebuilds the mount options parser, matches vfs_t lifetimes to fs_context, and removes support for the old mount path entirely. There is also a workaround for kernels that enforce "forbidden" mount options, and a fix to ensure Linux Security Modules get a chance to process mount options (#18376).
Other fixes worth noting include a resolution for read corruption after block cloning across a truncate (#18421), a use-after-free in dmu_write_direct_done() (#18440), a range tree corruption race in dnode_sync() (#18235), and a fix for the long-standing kernel BUG at mm/usercopy.c report (#18408). The release also adds proper support for POSIX_FADV_DONTNEED (#18399), with a follow-up patch handling single-block files correctly.
Binaries and source are available on the OpenZFS GitHub releases page. Administrators running dRAID pools or building against bleeding-edge kernels will want to look closely at this one, while users on older 2.4.x releases can upgrade in place.
