From owner-freebsd-current@freebsd.org Mon Jun 25 15:37:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A10CA1013AAC for ; Mon, 25 Jun 2018 15:37:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1203681C6D for ; Mon, 25 Jun 2018 15:37:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x229.google.com with SMTP id 128-v6so7056393itf.1 for ; Mon, 25 Jun 2018 08:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6UOpTS1CxKDnJmfPKZ0QslDIYVCF/fR7SIfXssP89Fo=; b=Cm/r9oWjwF0aZiz+FaiqLhtNhF/MKzgNhzGY8X4lhKWEBEz/Q5N7w5IUPO/GxmhIXc IYgYBoJQY3M+ZdjDieydtLy33lgI1I4g5ZOKfMPGtf9YsX0f1hHDUWxHXPrNePOgDbfi US2AxKiDU4VC7VQPPmag7ufeRqi7kR26R5OCMGHsGuQ2heQdirYRkR0RBYb0TA654QOV 4rqCguqP5LnR94Cqllu6hjfaWebvbVesYjAeMesdzsRoNO99Zm0J1JQ+sLft3iyOnQIQ l+tBmBChd2yzH4vd54M54Q+TA87li/jfniqLQDA5JUavYegiOQfsdOM4ONnQyLGxOjtC R01g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6UOpTS1CxKDnJmfPKZ0QslDIYVCF/fR7SIfXssP89Fo=; b=toXD4Utsf0xXFzeuw1EyYPvFqz/ufa1P1B2L9nzoLtSUcow8F33jtEZ9Etu+H+R5lx hlLBdnZqcaIDeH1lEBnI74Ou1AmepGVNl0R8LiC4MZtjko8ptMXUrTi/N4EnMHe8h89g nS3yKieT+HJvt6vBT/7bmkqL0APYmmB8G0WEVLZ9/X1JRWVLiaWNIG05RNHdKzVWPAzX C+coUEUxDPqg5xy9oTfeUc35SJ3XvH+55WaTVND+9UhofW6K+59n5a+3x3+wyHNjYqd8 Y5o6SJalYZSqXtfEDH6rSzwASZnnqBYp4H4bmh34IJ0mLsCIL3yU048J2pxVtu9EekXH Q5ow== X-Gm-Message-State: APt69E3dGxqVUyifyDaWRzfJmsn2mB2MfaI7ekfw/EKAN7afAoJRARe/ SsrfYYIJ7JaoB5g+Sj85K7bhWuiM3pHgsnRqkprNhQ== X-Google-Smtp-Source: AAOMgpdVyNdZAMt5auRURhPj01V6PnsPLittqxinubt/AtJgodCs4w8wLVkFineL6X3/3Bsk8UpBD9eEHAAfWE/9eqo= X-Received: by 2002:a24:64ce:: with SMTP id t197-v6mr1336283itc.36.1529941041389; Mon, 25 Jun 2018 08:37:21 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Mon, 25 Jun 2018 08:37:20 -0700 (PDT) X-Originating-IP: [50.227.106.226] In-Reply-To: <68667907-4698-c2f0-3d97-bb7f75ff6bbf@zyxst.net> References: <68667907-4698-c2f0-3d97-bb7f75ff6bbf@zyxst.net> From: Warner Losh Date: Mon, 25 Jun 2018 09:37:20 -0600 X-Google-Sender-Auth: EgakfG52YJ23ACE-ov6QxKzVis8 Message-ID: Subject: Re: ino64 To: tech-lists Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 15:37:23 -0000 On Mon, Jun 25, 2018 at 6:40 AM, tech-lists 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