From owner-freebsd-current@freebsd.org Fri Feb 12 01:57:47 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2BE5C53FA8C for ; Fri, 12 Feb 2021 01:57:47 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DcGpy5tgtz3kmf for ; Fri, 12 Feb 2021 01:57:46 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1lANiD-0000Bh-FV; Fri, 12 Feb 2021 01:57:37 +0000 Date: Fri, 12 Feb 2021 01:57:37 +0000 From: Gary Palmer To: "Russell L. Carter" Cc: freebsd-current@freebsd.org Subject: Re: upgrade stable/12 -> stable/13 zfs + boot partition Mediasize 64K Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 4DcGpy5tgtz3kmf X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Fri, 12 Feb 2021 01:57:47 -0000 On Thu, Feb 11, 2021 at 05:34:40PM -0700, Russell L. Carter wrote: > Greetings, > > I really want to jump from stable/12 to stable/13 but one thing is > causing a hesitancy. And that is, my main raidz2 system has > a system boot zfs mirror pair that has boot partition size > (Mediasize) of 64K, and when I tried to zpool upgrade that pool a > year or 2 ago I got some scary message something like "boot > partition size is not large enough". I asked about this on the > lists but never received an answer. So, laziness required me > to ignore the problem and not zpool upgrade any of my 15 or so > zpools in the interim. > > A few weeks ago I tried to make buildworld/installworld upgrade > 12->13 but the boot failed in the mounting filesystems phase with it > couldn't find a bootable target. So after restoring 12 I decided > to wait a bit. In the interim I have upgraded every zpool but that > one system pool. All the other freebsd-boot partitions have a size > of 512K. > > So what is the current advice? Is a freebsd-boot partition size > of 64K laughably obsolete, and I should get with the program and > repartition those disks, or can I march blindly into the upgrade? > > I guess I just want to understand where these sizes are going in > the future. Most layouts put a swap partition after the boot partition. If that is the case for you also, if you can disable the swapping to the swap partition you can probably increase boot and reduce swap size pretty easily. Otherwise you're probably going to have to split the mirror, repartition one drive, rebuild the mirror, reboot onto that drive and then do the same to the other drive. I've done it before on a headless system in a remote DC. With planning it's perfectly doable. I think I built a test vm in VirtualBox and made sure it all worked on that before trying it for real. Regards, Gary