I skipped last week due to Excessive System Administration, but here’s a snippet from OpenZFS Mastery.
Lucas’ virtualization host for testing this book ran bhyve on FreeBSD 14. FreeBSD 14 uses OpenZFS version 2.2, but the book you are reading right now had to include the RAIDZ expansion of OpenZFS 2.3. The newer OpenZFS was available as an add-on package. OpenZFS 2.3 can read OpenZFS 2.2 pools, but the reverse is not true. So long as the package and the kernel don’t fall out of synchronization, everything will work just fine. The odds of desynchronization are, eventually, one hundred percent, especially when destructively testing every option. The solution was to separate the zroot boot pool from those used for testing, . The zroot boot pool needed to remain compatible with …
I skipped last week due to Excessive System Administration, but here’s a snippet from OpenZFS Mastery.
Lucas’ virtualization host for testing this book ran bhyve on FreeBSD 14. FreeBSD 14 uses OpenZFS version 2.2, but the book you are reading right now had to include the RAIDZ expansion of OpenZFS 2.3. The newer OpenZFS was available as an add-on package. OpenZFS 2.3 can read OpenZFS 2.2 pools, but the reverse is not true. So long as the package and the kernel don’t fall out of synchronization, everything will work just fine. The odds of desynchronization are, eventually, one hundred percent, especially when destructively testing every option. The solution was to separate the zroot boot pool from those used for testing, . The zroot boot pool needed to remain compatible with the base system, while the drives used for virtualization and testing could be upgraded. Set compatibility property to lock the feature set to those supported by the base system.
Sponsorships for OpenZFS Mastery will not open until I ship out gifts for the last sponsorship. I don’t take money for a new thing until the previous new thing is complete. Stupid ethics!