Date: Wed, 8 Jul 2020 14:38:48 -0700 From: Matthew Macy <mmacy@freebsd.org> To: freebsd-fs <freebsd-fs@freebsd.org>, freebsd-hackers@freebsd.org, freebsd-current <freebsd-current@freebsd.org> Subject: Further note - Re: CFT for vendor openzfs Message-ID: <CAPrugNqJdGKVrtAHyHrBAvLYHgiV2B63=0FeH5vRbgeSwFCS0Q@mail.gmail.com> In-Reply-To: <CAPrugNp8xQiz-Sun0Z2Ay7H0qE_09jm1NFPJcgYmNH-fs5wezg@mail.gmail.com> References: <CAPrugNp8xQiz-Sun0Z2Ay7H0qE_09jm1NFPJcgYmNH-fs5wezg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Do NOT zpool upgrade unless you are willing to live without the ability to ever rollback to the legacy zfs kmod. On Wed, Jul 8, 2020 at 2:31 PM Matthew Macy <mmacy@freebsd.org> wrote: > > Checkout updated HEAD: > % git clone https://github.com/mattmacy/networking.git -b > projects/openzfs_vendor freebsd > > Checkout updated openzfs in to sys/contrib: > % git clone https://github.com/zfsonfreebsd/ZoF.git -b > projects/openzfs_vendor freebsd/sys/contrib/openzfs > > Build world and kernel with whatever your usual configuration is. > Where possible the openzfs kmod is backward compatible with the cmd > utils in HEAD so common operations work with existing tools and the > new kmod. In the projects/openzfs_vendor branch of ZoF ozfs libraries > are backward compatible with the zfs kmod in HEAD. Although ideally > one would test this in a separate boot environment, the > interoperability should allow one to rollback without too much > difficulty. > > Thanks in advance for your time. > -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPrugNqJdGKVrtAHyHrBAvLYHgiV2B63=0FeH5vRbgeSwFCS0Q>