From nobody Wed Nov 09 20:56:43 2022 X-Original-To: current@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 4N6y2K012Nz4XQ4p for ; Wed, 9 Nov 2022 20:56:57 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N6y2J349Nz4Fcl for ; Wed, 9 Nov 2022 20:56:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x635.google.com with SMTP id ud5so50239113ejc.4 for ; Wed, 09 Nov 2022 12:56:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FYeFu/7iypRQ8uOA3rBhzPjMv222e9QEN6Df5mQC/3w=; b=Gnc+rWNvao/V+LZY0wmkDTqCi6JbWzyd6e5eYsz0I8pQbWpX/qKGxhG3t5ci/hSXcs GqIs1EZa1QG06R8d7dGDooDcuQ1CtOd9QgD64xdKfq9TLKuoclZl32XwphNfvl1iYyAE CTXVY8GFc8LWLiAL++8q3NpGyDP4VeroctNGehAXsoguxAOOmZ0DTtkwsNKD5JYGMhlI nNXbZ7wwqvSPmONEO6EPbWQ7M/R8iItts5Um6MKq8acc2c7ikZjvdUFZ2oXyPqTQGlwA EILBAypQp6q8VlZ8/P/toPsE8qpmFSUEccofRukB8OEiN3gJWdQ/4RK5GdCNUJ1+t7nu 0h2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FYeFu/7iypRQ8uOA3rBhzPjMv222e9QEN6Df5mQC/3w=; b=eVtjKLtlH+ZBjviXMG224f0rbMQMopfSFGa5lZ/OJQget/p/uhHcRgtYaPbuPOcMcA OgquDz+AxK/vTrS2drcHFfZ7bN+usVOnCtMlrV+YB4QyKPts2m1g1OQyTltfP+tkvfOD g763wcSkhXHSlSjHU3bMc3/haALmX95Coz2Q5JQWh4uYVqtSqvDeFozwRSFv2EmwlV80 8o2sDLWaNK20rE12vp8lYYoEt6dVKGFwZldQC7POXsq5cCppaPUvXusxFiXoks25CExE LO7qf/3maUdjdUJ32i1uvqPdKzl70dkuDyqBAEFteREWQjXhP7A62MBe9HR9clWuZz4b kvHg== X-Gm-Message-State: ACrzQf2FJ1oxNwaOGf6wADpiSgHMxwUkpkWj4oLn/0Mdr/WwyW0rCXL4 yDjKzjngLnPa2GgtCUcrmk+o+k+xGWMKKe7142tLfA== X-Google-Smtp-Source: AMsMyM7DnCCizAeFcJOh6U6kK6TTADA0h56aQxAJUA4PNo2fEkImB5Q9RqeHWk1FMxiEpqvHwCQqHKMlKkB7rKVUxCk= X-Received: by 2002:a17:906:9d14:b0:799:9ace:e868 with SMTP id fn20-20020a1709069d1400b007999acee868mr1676803ejc.451.1668027414359; Wed, 09 Nov 2022 12:56:54 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202211070339.2A73dJlO027991@gitrepo.freebsd.org> <20221107121514.Horde.nulS9Wg1s3yzAsXXkuJRBa9@webmail.leidinger.net> <20221108105053.Horde.eqgFiBJe2ngGAj6BkXcv5-Z@webmail.leidinger.net> <20221109134610.Horde.JB7ibQTWprHbmIUfhg7JY7f@webmail.leidinger.net> <460205F9-5D59-4033-813B-C34E01BFD6C4@hausen.com> In-Reply-To: From: Warner Losh Date: Wed, 9 Nov 2022 13:56:43 -0700 Message-ID: Subject: Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script) To: "Patrick M. Hausen" Cc: Alexander Leidinger , Mark Millard , tsoome@freebsd.org, Li-Wen Hsu , current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008250c205ed0fe5f7" X-Rspamd-Queue-Id: 4N6y2J349Nz4Fcl X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-ThisMailContainsUnwantedMimeParts: N --0000000000008250c205ed0fe5f7 Content-Type: text/plain; charset="UTF-8" On Wed, Nov 9, 2022 at 1:54 PM Patrick M. Hausen wrote: > Hi Warner, > > > Am 09.11.2022 um 21:51 schrieb Warner Losh : > > Yes. For safety, boot loader upgrade is mandatory when you do a zpool > upgrade of the root filesystem. > > It was definitely needed in the OpenZFS jump, and we've had one or two > other flag days since. > > That's a given and not a problem. What I fear from my understanding of > this thread so far is > that there might be a situation when I upgrade the zpool and the boot > loader and the system > ends up unbootable nonetheless. > > Possible or not? > If all you do is upgrade, then no, modulo bugs that we've thankfully not had yet. It's when you enable something on the zpool that you can run into trouble, but that's true independent of upgrade :) Warner > Modulo bugs, try test systems first, etc. Of course. > > Thanks, > Patrick --0000000000008250c205ed0fe5f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Nov 9, 2022 at 1:54 PM Patric= k M. Hausen <pmh@hausen.com> wr= ote:
Hi Warner,<= br>
> Am 09.11.2022 um 21:51 schrieb Warner Losh <imp@bsdimp.com>:
> Yes. For safety, boot loader upgrade is mandatory when you do a zpool = upgrade of the root filesystem.
> It was definitely needed in the OpenZFS jump, and we've had one or= two other flag days since.

That's a given and not a problem. What I fear from my understanding of = this thread so far is
that there might be a situation when I upgrade the zpool and the boot loade= r and the system
ends up unbootable nonetheless.

Possible or not?

If all you do is upgra= de, then no, modulo bugs that we've thankfully not had yet. It's wh= en you enable something on the zpool that you can run into trouble, but tha= t's true independent of upgrade :)

Warner
=C2=A0
Modulo bugs, try test systems first, etc. Of course.

Thanks,
Patrick
--0000000000008250c205ed0fe5f7--