From nobody Mon Aug 22 12:10:00 2022 X-Original-To: freebsd-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 4MBB4y0tCnz4ZT6p for ; Mon, 22 Aug 2022 12:10:10 +0000 (UTC) (envelope-from SRS0=7PgN=Y2=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 4MBB4w5Gz1z3w6b; Mon, 22 Aug 2022 12:10:08 +0000 (UTC) (envelope-from SRS0=7PgN=Y2=klop.ws=ronald-lists@realworks.nl) Date: Mon, 22 Aug 2022 14:10:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1661170201; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uvIpA5dZSZvyw3oYbmuE8M0bsBxdviwdgQqjbkothWw=; b=oUoRFbPHzYGy+fSGLgUHyEmm5tnBJhrNSpaiaUtt4D8OdHKZvqlGeqVGrQaTw8TcQ+0G6r /UklSlrHtUR+pXfOy7nWxgWSIUjzO4rk+4UfpWsoggaF0wvZRWJ2AS0vYlr5e/XSL5mi47 wRzvLR1KkaLv+0BNnah9djR+dULXK5kGNq4ImSHyv/+rR+bjmXxYEkecWA5yEsM1OOj040 TJAWEyJ4QFEZ42TMEJ3zBmRG59kjTUyIG4qjGSRVPKEEVIKoEuOdSnvjyL/SlgUgBEm6/N VacOVAuM6cEm0sOA1X/rZgbwn7zC3NgFw4YeZOShWPUqq/aTs2Y+fQb4gk1oEA== From: Ronald Klop To: Peter Jeremy Cc: freebsd-current@freebsd.org, Ryan Moeller , "Patrick M. Hausen" Message-ID: <623263165.219.1661170200563@localhost> In-Reply-To: References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> Subject: Re: Beadm can't create snapshot 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 Content-Type: multipart/alternative; boundary="----=_Part_218_843763257.1661170200558" X-Mailer: Realworks (620.114) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4MBB4w5Gz1z3w6b X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=oUoRFbPH; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=7PgN=Y2=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=7PgN=Y2=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.19 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.998]; NEURAL_HAM_SHORT(-0.99)[-0.995]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=7PgN=Y2=klop.ws=ronald-lists@realworks.nl]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_HAS_DN(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; RCPT_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=7PgN=Y2=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_218_843763257.1661170200558 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Peter Jeremy Datum: maandag, 22 augustus 2022 10:45 Aan: "Patrick M. Hausen" CC: Ryan Moeller , freebsd-current@freebsd.org Onderwerp: Re: Beadm can't create snapshot > > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote: > >Isn't beadm retired in favour of bectl? > > bectl still has a number of bugs: > 1) The output from "bectl list" is in filesystem/bename order rather > than creation date order. This is an issue if you use (eg) git > commit hashes as the name. > 2) "bectl activate" doesn't update /boot/loader.conf so the wrong > root filesystem is mounted. > > That said "bectl create" appears to be a workable replacement for > "beadm create" and avoids the current "'snapshots_changed' is > readonly" bugs. > > -- > Peter Jeremy > > > > Hi, >From man bectl: activate [-t | -T] beName Activate the given beName as the default boot filesystem. If the -t flag is given, this takes effect only for the next boot. Flag -T removes temporary boot once configuration. Without temporary configuration, the next boot will use zfs dataset specified in boot pool bootfs property. So it uses the bootfs property instead of loader.conf. If beadm used a different mechaniscm it would by nice to mention that in the HISTORY section of the bectl man page. Regards, Ronald. ------=_Part_218_843763257.1661170200558 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

Van: Peter Jeremy <peterj@freebsd.org>
Datum: maandag, 22 augustus 2022 10:45
Aan: "Patrick M. Hausen" <pmh@hausen.com>
CC: Ryan Moeller <freqlabs@freebsd.org>, freebsd-current@freebsd.org
Onderwerp: Re: Beadm can't create snapshot

On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" <pmh@hausen.com> wrote:
>Isn't beadm retired in favour of bectl?

bectl still has a number of bugs:
1) The output from "bectl list" is in filesystem/bename order rather
   than creation date order.  This is an issue if you use (eg) git
   commit hashes as the name.
2) "bectl activate" doesn't update /boot/loader.conf so the wrong
   root filesystem is mounted.

That said "bectl create" appears to be a workable replacement for
"beadm create" and avoids the current "'snapshots_changed' is
readonly" bugs.

-- 
Peter Jeremy
 


Hi,

>From man bectl:
     activate [-t | -T] beName
               Activate the given beName as the default boot filesystem.  If
               the -t flag is given, this takes effect only for the next boot.
               Flag -T removes temporary boot once configuration.  Without
               temporary configuration, the next boot will use zfs dataset
               specified in boot pool bootfs property.

So it uses the bootfs property instead of loader.conf. If beadm used a different mechaniscm it would by nice to mention that in the HISTORY section of the bectl man page.

Regards,
Ronald.
  ------=_Part_218_843763257.1661170200558--