Hey Anil,

Hope exam week wasn't as crazy as I remember it being when I was teaching. Let me know when would be a good time to connect re: ZFS.

I even got to meet Xe in person a few weeks ago at @bsdcan.bsky.social. FreeBSD uses Anubis to protect our cgit, bugzilla, and the like, as they were getting bombarded.

Time to look at mdo man.freebsd.org/cgi/man.cgi?...

It is the way git works, I am not sure what to tell you.

ZFS would be unaware of the inactive path, as it sits on top of GEOM

I am saying every commit to the upstream OpenZFS repo is replicated into the FreeBSD repo unchanged, with the original commit message (and author)

Damn autocorrect, that should say "Vendoring" process

As you likely know, FreeBSD uses the "censoring" process to include 3rd party software.

That means it contains a complete copy from upstream.

Are you also going to complain about OpenSSL commits that are fixes for Linux?

OpenSSH commits that only impact OpenBSD?

It is part of tracking upstream.

Your view seems rather distorted.
The relatime change didn't impact FreeBSD and zfsd is FreeBSD specific, so you can't blame OpenZFS.

If you are having issues, I would recommend contacting KlaraSystems.com for FreeBSD specific ZFS support and big fixing

zfsd is a FreeBSD only feature. The change was made by a FreeBSD developer working at a FreeBSD enterprise user.

Why is your fabric resulting in an I/O taking 30 seconds?

I don't know what you are talking about here.

This has absolutely no impact on FreeBSD, there is no such thing as 'relative atime' on FreeBSD.