Date: Sat, 2 Dec 2023 19:11:48 -0500 From: "Mark E. Mallett" <mem@schmem.com> To: freebsd-stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: <ZWvHxOiy5VYRY63w@schorl.qozzy.net> In-Reply-To: <ZWsI4SbNU2xPjaPF@marvin.hueftgold.tld> References: <20231201031737.DF0231B942@freefall.freebsd.org> <ZWsI4SbNU2xPjaPF@marvin.hueftgold.tld>
next in thread | previous in thread | raw e-mail | index | archive | help
Might I also ask (or say):
I find some of the notice and actions confusing, at least in minor ways.
I'm mainly only remarking since the subject has been opened.
First, "Background" talks about FreeBSD 12 ZFS being based on Illumos
ZFS, and 13 and on being based on OpenZFS. I kinda wish the notice would
say why it tells me that, because the implication in the text is that
both are affected. It would be nice if it said "both are affected"
right out in the open. I realize it's implied.
Second, it gives workaround of "vfs.zfs.dmu_offset_next_sync sysctl to 0"
But on my 12.4 systems there is no such sysctl variable.
Third, it says the binary upgrade will result in 12.4-RELEASE-p8. When
I do the freebsd-update, the result according to uname is
12.4-RELEASE-p6. Thinking that perhaps I have to do it again, I am told
No updates needed to update system to 12.4-RELEASE-p8
and yet uname -a still says 12.4-RELEASE-p6. Somebody might ask if
I did a reboot, and yes.
(and there's still no vfs.zfs.dum_offset variable)
Like I said, all pretty minor except maybe the sysctl variable one.
I'm mostly bothered because I'm overly literal and/or anal.
I was starting from p1. I hadn't seen anything urging me to step up
to a different patch level, hopefully I hadn't overlooked anything.
-mm- (long time no post)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZWvHxOiy5VYRY63w>