From nobody Sat Nov 25 00:40:56 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ScY1l32mmz528p7 for ; Sat, 25 Nov 2023 00:41:15 +0000 (UTC) (envelope-from freebsd@gushi.org) Received: from prime.gushi.org (prime.gushi.org [IPv6:2620:137:6000:10::142]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "prime.gushi.org", Issuer "RapidSSL Global TLS RSA4096 SHA256 2022 CA1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ScY1j73msz3d6Q for ; Sat, 25 Nov 2023 00:41:13 +0000 (UTC) (envelope-from freebsd@gushi.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gushi.org header.s=prime2014 header.b=iIomudQD; spf=pass (mx1.freebsd.org: domain of freebsd@gushi.org designates 2620:137:6000:10::142 as permitted sender) smtp.mailfrom=freebsd@gushi.org; dmarc=pass (policy=none) header.from=gushi.org Received: from smtpclient.apple (high.availability.mobile.mustelid.operational.command.kiosk.isc.org [149.20.66.196]) (authenticated bits=0) by prime.gushi.org (8.17.2/8.17.2) with ESMTPSA id 3AP0f75h051363 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sat, 25 Nov 2023 00:41:07 GMT (envelope-from freebsd@gushi.org) DKIM-Filter: OpenDKIM Filter v2.10.3 prime.gushi.org 3AP0f75h051363 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gushi.org; s=prime2014; t=1700872867; bh=P4SITFr1YcLUpPmO7lQgBSwyujXXIRZ2lRDb21bRBb4=; h=From:Subject:Date:To; z=From:=20"Dan=20Mahoney=20(Ports)"=20|Subject:= 20ZFS=20upgrade=20loader=20actions=20--=20is=20it=20possible=20to= 20check=20before=20reboot=0D=0A=20if=20your=20system=20will=20rebo ot=20cleanly?|Date:=20Fri,=2024=20Nov=202023=2016:40:56=20-0800|To :=20questions@freebsd.org; b=iIomudQDdJyHOm5rIXf7u5iOcUKp+kIYR1dAO0Zp+pm+3RTVsRBa1nANCGxlKRPpA 8KtRINHurZ7QnPadi+hXwd7WFZe5ET0QvqIOJ/SjQKfcT8HEjp6r8bgXP31nsPaNX9 Hw65EdRo19jtWHgS06eVLWU+HzG/ySJZANHmEX4qSAKrEVOvFwE+Q5wF2A22n8d4ic Xtkrci7F6YFYzkzljceTN0OY9B1DxJFWmJV0H5/qPYCREzREB45BQ0upm4DpIw9UKB tCyp8141wwGG+L3l9JIYgsQWt4adDGiyVI9hN2/Q3LY32aHp1blUV45dhTnYAr5jbl jFghbNSjlk59A== X-Authentication-Warning: prime.gushi.org: Host high.availability.mobile.mustelid.operational.command.kiosk.isc.org [149.20.66.196] claimed to be smtpclient.apple From: "Dan Mahoney (Ports)" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: ZFS upgrade loader actions -- is it possible to check before reboot if your system will reboot cleanly? Message-Id: Date: Fri, 24 Nov 2023 16:40:56 -0800 To: questions@freebsd.org X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Result: default: False [-5.09 / 15.00]; DWL_DNSWL_MED(-2.00)[gushi.org:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.989]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gushi.org,none]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[gushi.org:s=prime2014]; RCVD_IN_DNSWL_MED(-0.20)[2620:137:6000:10::142:from]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:393507, ipnet:2620:137:6000::/44, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[gushi.org:+]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4ScY1j73msz3d6Q X-Spamd-Bar: ----- I was reading a couple recent threads (one about upgrading from 13.2 to = 14) and another more virtiolic thread about how terrible, awful, no-good = our documentation is. I don=E2=80=99t agree with this. =20 I shied away from Linux for years because of nonfunctional man pages, or = man pages that someone bothered to write, but then to only point to a = postscript file on disk, or to point at an =E2=80=9Cinfo=E2=80=9D file. = I mused regularly that it=E2=80=99s sad that =E2=80=9CThe Linux = Documentation Project=E2=80=9D website is in fact a whole different = website from =E2=80=9CThe Linux Project=E2=80=9D=E2=80=A6or any hundred = of Linux Projects. =20 Anyway, both threads talked about zpool upgrades and needing to update = your bootloader. I was recently bitten by this, requiring my datacenter = to put a physical disc in a drive for me to recover from. (And I even = had to ship them a USB cdrom drive =E2=80=94 don=E2=80=99t get me = started on supermicro=E2=80=99s virtual media implementation. it=E2=80=99= s bad). I understand that printing the raw commands to upgrade your boot loader = (and/or your pmbr) as part of the output of a successful =E2=80=9Czpool = upgrade=E2=80=9D is probably a bad idea, as the commands are not = one-size-fits-all, but having a special manpage for this process, = specifically (and having zpool upgrade point at that page) might be = useful.=20 If the handbook doesn=E2=80=99t say something about this process, then = it should as well. But also, it would be really nice to be able to poll the version of the = various components that are actually installed on the system (the boot = loader, and even the pmbr if you have one) and see if they=E2=80=99re = current and can support the current version of your boot pool. I don=E2=80=99t know if this is possible. Gpart bootcode, for example, = only has a command to *install* the bootcode, not read it back. Since = the loader and the mbr are tiny, highly optimized pieces of code, I = don=E2=80=99t know if there are any strings that can be examined to see = if they match the running system. But if the tools don=E2=80=99t exist, = they should =E2=80=94 even absent any version strings, if nothing else, = gpart bootcode should be able to non-intrusively compare a file with the = already existing one. Does anyone know for sure? -Dan=