Re: FreeBSD, Illumos ZFS, and OpenZFS

On 2/24/24 04:40, Dag-Erling Smørgrav wrote:
> David Christensen  writes:
>> mike tancsa writes:
>>> David Christensen writes:
>>>> My avoidance of OpenZFS has been reaffirmed.  I do not want my
>>>> data on OpenZFS.
>>> TBH, you are overthinking this.
>> Given two severe bugs in four months, it does not require much
>> thought to conclude that OpenZFS places data at risk.
> 
> For the love of all that's holy, stop reading Phoronix, it's the 
> National Enquirer of F/OSS.
> 
> DES


I'm with Kay:

https://www.youtube.com/watch?v=duA5eWjHCjU


>>>> If I use a FreeBSD 13-2-R installer to create a new FreeBSD instance 
>>>> with ZFS file systems and without native encryption:
>>>> 
>>>> 1.  Will the installed FreeBSD instance contain corrupt files?
>>>> 
>>>> 2.  Will the installed FreeBSD instance contain OpenZFS bug #15526?


Looking at the FreeBSD 13.2-RELEASE Announcement:

     https://www.freebsd.org/releases/13.2R/announce/

     ZFS has been upgraded to OpenZFS release 2.1.9.


Looking at the OpenZFS bug report #15526:

     https://github.com/openzfs/zfs/issues/15526

     OpenZFS Version 	2.2.0


If I do not use OpenZFS native encryption per OpenZFS documentation 
issue #494, I conclude the answer to question #1 is "No".


I prefer packages.  Looking at the FreeBSD-EN-23:16.openzfs Errata Notice:

 
https://www.freebsd.org/security/advisories/FreeBSD-EN-23:16.openzfs.asc

     1) To update your system via a binary patch:

     Systems running a RELEASE version of FreeBSD on the amd64 or arm64 
platforms, or the i386 platfrom on FreeBSD 13 and earlier, can be 
updated via the freebsd-update(8) utility:

     # freebsd-update fetch
     # freebsd-update install
     # shutdown -r +10min "Rebooting to apply OpenZFS erratum update"


I conclude the answer to question #2 is "Yes"; but a documented fix can 
be applied after installation to resolve OpenZFS issue #15526.


David