(removed larger list of accounts not related to this subthread)

@TurboTrain Well 😒 ...

"Oh, No! Not #OpenZFS?!"

"Et tu, OpenZFS?"

"Slop comes for every project."

@[email protected] With https://mastodon.social/@bms48/116662724883486066 in consideration, you are now moving goal posts, or accepting the increasing use bit by bit -- pick as suitable.

#whatHaveYouSloppedLately?🤨

One ZAP entry. One uint64_t in spa_t. One new CLI flag.

That's all it took to teach #OpenZFS to skip blocks the last scrub already verified.

`zpool scrub -C` ships in 2.4.0.

https://oshogbo.com/blog/89/

#FreeBSD #Linux #sysadmin #devops #storage

Don't Make ZFS Re-Read What It Just Read

I have already mentioned one of my improvements to scrub in an earlier post, Teaching ZFS about time. In that post I also claimed that scrub can be expensive, and that we were looking for ways to limit the amount of data we actually want to scrub. A scrub on a multi-petabyte pool can run for days, and some of us want a smaller, easier check that everything is still going right.

Proxmox Server Solutions

Proxmox develops powerful and efficient open-source server solutions like the Proxmox VE platform, Proxmox Backup Server, and Proxmox Mail Gateway.

Proxmox
I do enjoy how I can beat the hell out of a FreeBSD box and it just takes it without flinching

#FreeBSD #OpenZFS #ZFS

My grant application to work on #OpenZFS and #FreeBSD/#ARM64 documentation has been waitlisted.

Might any patrons want to support this work?

Proxmox Server Solutions

Proxmox develops powerful and efficient open-source server solutions like the Proxmox VE platform, Proxmox Backup Server, and Proxmox Mail Gateway.

Proxmox

The recording of the May 20th, 2026 #OpenZFS Production User Call is up:

https://youtu.be/Mhu9WllvEes

We discussed Rob Norris' extensive refactoring of the OpenZFS ZAP code with related testing infrastructure, eZFS2A multi-factor authentication for encrypted datasets, ZFSObjectIdToPath, OpenZFS on Windows support for VSS and Hyper-V, a scale-out architecture, 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

2026-05-20 OpenZFS Production User Call

YouTube

@robn *ugh* Personally prefer to have "readonly=on" to supersede read-write option of "{zfs-,}mount" commands.

Issue 18557 is really not an issue. "Affected" people ought to not-do-that-if-it-hurts. (Actually, same could be said of my preference (that I ought to not use "{zfs-,}mount" with read-write option on a dataset with "readonly=on" property).)

Anyway, what good is "readonly" property (set to "on") then if it is easily overridden.

#OpenZFS #ZFS

Ever wondered how the #OpenZFS readonly filesystem property interacts with the ro and rw mount options, and if using mount(8) vs zfs-mount(8) changes anything, and if your choice of platform changes anything?

I certainly hadn't, until I got a bug report that I'd subtly changed a couple of cases in 2.4.2 for Linux. I unbroke it, but not before spending a bunch of time trying to figure out what "unbroke" means. Emphasis on "trying".

Here's the fix, with my endless 🤔 in the collapsed "bonus" section. Good speluncking opportunity available if you'd like to figure it out!

https://github.com/openzfs/zfs/pull/18563

linux/super: properly apply ro/rw mount option to superblock by robn · Pull Request #18563 · openzfs/zfs

[Sponsors: TrueNAS] Motivation and Context f5a9e3a changed how SB_RDONLY was applied to the new mount in a way that was too simplistic - it only sets readonly on the filesystem if the mount was ro,...

GitHub