🦾 OpenZFS 2.3.4 Brings Linux 6.16 Kernel Compatibility, "zfs rewrite" Command - Phoronix

「 OpenZFS 2.3.4 brings support for the latest Linux 6.16 stable kernel where as the prior 2.3.3 release tapped out at Linux 6.15. OpenZFS 2.3.4 continues to support back to the Linux 4.18 kernel as well as FreeBSD 13.3 and newer, including the upcoming FreeBSD 15.0 」

https://www.phoronix.com/news/OpenZFS-2.3.4-Released

#openzfs #freebsd #linux #opensource

And so the #OpenZFS 2.4 series begins.

This could be one of the most significant releases in years. At least, I think zfs rewrite is a game changer for ongoing pool maintenance, and a huge amount of work has gone into stability and correctness when the pool is damaged or suspended (closing so many ancient bug reports along the way).

I'll try to write more about it soon. For now thiygh, go try it out and let us know how you like it! 💚

https://github.com/openzfs/zfs/releases/tag/zfs-2.4.0-rc1

And so the #OpenZFS 2.4 series begins.

This could be one of the most significant releases in years. At least, I think zfs rewrite is a game changer for ongoing pool maintenance, and a huge amount of work has gone into stability and correctness when the pool is damaged or suspended (closing so many ancient bug reports along the way).

I'll try to write more about it soon. For now thiygh, go try it out and let us know how you like it! 💚

https://github.com/openzfs/zfs/releases/tag/zfs-2.4.0-rc1

The 2025 #OpenZFS User and Developer Summit is rapidly approaching!

Please book your travel and register.

Developers should have received the CfP from Matt and please reach out if you have not.

User participation is discussed in the open on the Production User Calls every week.

See you there!

https://openzfs.org/wiki/OpenZFS_Developer_Summit

With the recent #OpenZFS import into #FreeBSD main, Solaris-style named attributes are now supported. This means, for #ZFS datasets configured for this new feature, developers would call open(2) to open the named attribute (aka, filesystem extended attribute) as a file descriptor. One can use normal syscalls like read(2), write(2), lseek(2), etc. to interact with the attribute.

This provides a unique venue for stealthy code injection techniques. By combining Solaris-style named attributes with fdlopen(3), attackers can inject shared objects that are difficult to inspect via normal methods.

We have mitigated this kind of technique in #HardenedBSD by hardening the RTLD, teaching it to disallow any attempt to call fdlopen(3) on a named attribute file descriptor: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/commit/4fec880a91e389a5bf6d5849c2b27e0f31a7d3ed

The FreeBSD commit that introduced the plumbing for Solaris-style named attributes: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/commit/2ec2ba7e232dd126df0617194fd07be78c7a2ab9

The FreeBSD commit merging in the latest OpenZFS code with the Solaris-style named attribute feature implemented: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/commit/df58e8b1506f241670be86a560fb6e8432043aee

#infosec

With the recent #OpenZFS import into #FreeBSD main, Solaris-style named attributes are now supported. This means, for #ZFS datasets configured for this new feature, developers would call open(2) to open the named attribute (aka, filesystem extended attribute) as a file descriptor. One can use normal syscalls like read(2), write(2), lseek(2), etc. to interact with the attribute.

This provides a unique venue for stealthy code injection techniques. By combining Solaris-style named attributes with fdlopen(3), attackers can inject shared objects that are difficult to inspect via normal methods.

We have mitigated this kind of technique in #HardenedBSD by hardening the RTLD, teaching it to disallow any attempt to call fdlopen(3) on a named attribute file descriptor: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/commit/4fec880a91e389a5bf6d5849c2b27e0f31a7d3ed

The FreeBSD commit that introduced the plumbing for Solaris-style named attributes: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/commit/2ec2ba7e232dd126df0617194fd07be78c7a2ab9

The FreeBSD commit merging in the latest OpenZFS code with the Solaris-style named attribute feature implemented: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/commit/df58e8b1506f241670be86a560fb6e8432043aee

#infosec

The recording of the July 31st, 2025 #bhyve Production User Call is up:

https://youtu.be/B7DsDvx95dY

We discussed recent Production User Calls and upcoming events, Eurobhyvecon, Major CPU ID progress and reviews, paravirtualized clocks, #OpenZFS replication with Zelta, devd events in #FreeBSD and their equivalents in #illumos, VM metadata collection, and more!

"Don't forget to slam those Like and Subscribe buttons."

The recording of the July 31st, 2025 #bhyve Production User Call is up:

https://youtu.be/B7DsDvx95dY

We discussed recent Production User Calls and upcoming events, Eurobhyvecon, Major CPU ID progress and reviews, paravirtualized clocks, #OpenZFS replication with Zelta, devd events in #FreeBSD and their equivalents in #illumos, VM metadata collection, and more!

"Don't forget to slam those Like and Subscribe buttons."

I don't know if anybody noticed #ZeroFS yet, but it seems there is a completely user space-implementation of #NFS and #blockstorage on top of #S3 #objectstorage: https://github.com/Barre/zerofs

Including a demo running #ZFS on top of it which essentially allows geo-redundant ZFS volumes: https://asciinema.org/a/728234 & https://github.com/Barre/zerofs?tab=readme-ov-file#geo-distributed-storage-with-zfs

I don't see no #FreeBSD port yet, but if that really works it would be absolutely awesome.

#OpenZFS

Once again today, #FreeBSD and #ZFS saved a setup. Suddenly, a colleague realized that a database was acting up - probably some massive operation had deleted something. The machine takes snapshots every 15 minutes and keeps them for a few hours, then one a day and keeps those for days. To make a long story short, the July 4th dump still had the correct data. To get there, we just had to clone all the snapshots (going back day by day) and test them.

Snapshots are one of the best inventions since sliced bread.

#RunBSD#OpenZFS

The recording of the June 25th, 2025 #OpenZFS Production User Call is up:

https://youtu.be/qQF2QkPfBko

We discussed ZFS on ZFS virtual machine block size alignment and caching, User and Developer Summit wish list items, including channel program features, illumos OpenZFS, libzfs, Samba VSS, flexible zpool history logging, FreeBSD NFSd auditing, a manual page proposal, and more!

"Don't forget to slam those Like and Subscribe buttons."