From owner-freebsd-current@freebsd.org Fri Feb 12 03:13:37 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 6CF21541124 for ; Fri, 12 Feb 2021 03:13:37 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (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 4DcJVS3tgLz3pr6 for ; Fri, 12 Feb 2021 03:13:36 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from [10.0.10.15] (unknown [10.0.10.15]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 289008A87 for ; Thu, 11 Feb 2021 20:13:34 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pinyon.org; s=dkim; t=1613099614; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WDOtxKDu0OrjHaEH4duFPJVFEc1VEr40oK7pWvjYkuU=; b=gXLlon823O3GCpAMmBuGZASBgC8dYvpBG2Oz0/8Zn6zJBqnLDpYGgHYyBWvOzFOMQdbY1F 1C+Afe7RUAPBSlW5kyKzKYMK8CT6aLtxpe6lGx+a5LGfCY1JguwB9wzGo969JY4tdsY7YW STDx8sZAZcwm712ISEEuCAdYB07mS2U= Subject: Re: upgrade stable/12 -> stable/13 zfs + boot partition Mediasize 64K To: freebsd-current@freebsd.org References: From: "Russell L. Carter" Message-ID: <6cd9f937-1bcc-3f50-87dc-fcbf038dff6a@pinyon.org> Date: Thu, 11 Feb 2021 20:13:33 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.10 X-Rspamd-Server: h2 X-Rspamd-Queue-Id: 4DcJVS3tgLz3pr6 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pinyon.org header.s=dkim header.b=gXLlon82; dmarc=none; spf=pass (mx1.freebsd.org: domain of rcarter@pinyon.org designates 65.101.20.170 as permitted sender) smtp.mailfrom=rcarter@pinyon.org X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[pinyon.org:s=dkim]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[65.101.20.170:from:127.0.2.255]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[pinyon.org:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[pinyon.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[65.101.20.170:from]; ASN(0.00)[asn:209, ipnet:65.101.0.0/18, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] 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 03:13:37 -0000 On 2/11/21 7:46 PM, Dennis Clarke via freebsd-current wrote: > On 2/11/21 8:57 PM, Gary Palmer wrote: >> 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. >> > > The process is trivial with ZFS and a mirror setup. No need to reboot. > Think of the mirror as a "left" and "right" side. If you have a three > way mirror than you are singing in the rain. Regardless just break the > mirror. Do whatever you want with the disks that are now free and clear > of the previous mirror config. Use gpart and set them up with whatever > you need. Then attach the disk(s) back onto the mirror and wait for the > thing to re-silver. Run a scrub if you want. Depends on the size. Just > know that a large amount of storage ( more than 64T ) will take a long > time to scrub and for that matter a long time to re-silver. Maybe a day. > Once everything is re-synced as a mirror just repeat the process on the > other side of the mirror. No need to reboot until you feel like testing > the whole show. > > This sort of situation is also a good reason to use three way mirrors > with a hot spare pool. When possible. Makes the whole process entirely > worry free and nothing more than a cup of coffee to ponder it. > > For the sake of details what does "gpart show" report? Here you go: root@terpsichore> gpart show => 34 625142381 da0 GPT (298G) 34 128 1 freebsd-boot (64K) 162 8388608 2 freebsd-swap (4.0G) 8388770 616753645 3 freebsd-zfs (294G) => 34 625142381 da1 GPT (298G) 34 128 1 freebsd-boot (64K) 162 8388608 2 freebsd-swap (4.0G) 8388770 616753645 3 freebsd-zfs (294G) => 34 5860533101 da2 GPT (2.7T) 34 6 - free - (3.0K) 40 5860533088 1 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5K) => 40 5860533088 da3 GPT (2.7T) 40 5860533080 1 freebsd-zfs (2.7T) 5860533120 8 - free - (4.0K) => 40 5860533088 da4 GPT (2.7T) 40 5860533088 1 freebsd-zfs (2.7T) => 40 5860533088 da5 GPT (2.7T) 40 5860533088 1 freebsd-zfs (2.7T) => 40 5860533088 da6 GPT (2.7T) 40 5860533088 1 freebsd-zfs (2.7T) => 40 5860533088 da7 GPT (2.7T) 40 5860533088 1 freebsd-zfs (2.7T) root@terpsichore> I'm interested in any comments, if appropriate. This now 7(!!) year old system with 6 drive replacements over time on the raidz2, quite tiny and I guess entirely obsolete. But it's paid for, does its job. These days I might go with a 2 or 3 drive mirror. Thanks, Russell > > > Dennis Clarke > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >