Date: Mon, 25 Jun 2018 09:37:20 -0600 From: Warner Losh <imp@bsdimp.com> To: tech-lists <tech-lists@zyxst.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ino64 Message-ID: <CANCZdfoj8COo=99H78ST5esPKWmdvsG2J4_uoMd3tiYvsbWC8g@mail.gmail.com> In-Reply-To: <68667907-4698-c2f0-3d97-bb7f75ff6bbf@zyxst.net> References: <68667907-4698-c2f0-3d97-bb7f75ff6bbf@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 25, 2018 at 6:40 AM, tech-lists <tech-lists@zyxst.net> wrote: > Hello, > > When upgrading an old-ish 12-current (r317212), as per: > > 20170523: >> The "ino64" 64-bit inode project has been committed, which extends >> a number of types to 64 bits. In order to upgrade, carefully >> follow >> the full procedure documented below under the heading "To rebuild >> everything and install it on the current system." Specifically, a >> reboot is required after installing the new kernel before >> installing >> world. >> > > is there anything more specific I need to do as well, like rebuild all > installed ports? > While the compat stuff generally works, there are edge cases where it will fail when you have a mixed environment. You're best bet is to reinstall all ports. If you do just a few, you'll hit the edge cases. > The system runs ZFS. It is *not* root-on-ZFS though. Is there anything > more I need to consider for this? > No, the change is agnostic to that. > The system also runs bhyve. Are there any special considerations I need to > bear in mind for the guest VMs? > No, unless they too are upgrade across the barrier. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoj8COo=99H78ST5esPKWmdvsG2J4_uoMd3tiYvsbWC8g>