Date: Tue, 23 Aug 2022 15:19:34 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Kyle Evans <kevans@freebsd.org> Cc: freebsd-current@freebsd.org, Ryan Moeller <freqlabs@freebsd.org>, "Patrick M. Hausen" <pmh@hausen.com>, Peter Jeremy <peterj@freebsd.org> Subject: Re: Beadm can't create snapshot Message-ID: <2078216761.314.1661260774009@localhost> In-Reply-To: <CACNAnaEcr=9Ua8z%2BGC10pOeBAiDhkaOENEA_GQHpu-X1dxRXeQ@mail.gmail.com> References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> <C4A81AF9-2C11-4931-B5D9-1B257AB583DF@hausen.com> <YwNCQSL5PmvO2nOs@server.rulingia.com> <623263165.219.1661170200563@localhost> <CACNAnaEcr=9Ua8z%2BGC10pOeBAiDhkaOENEA_GQHpu-X1dxRXeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_313_1242291649.1661260773941 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Kyle Evans <kevans@freebsd.org> Datum: maandag, 22 augustus 2022 17:11 Aan: Ronald Klop <ronald-lists@klop.ws> CC: Peter Jeremy <peterj@freebsd.org>, freebsd-current@freebsd.org, Ryan Moeller <freqlabs@freebsd.org>, "Patrick M. Hausen" <pmh@hausen.com> Onderwerp: Re: Beadm can't create snapshot > > On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop <ronald-lists@klop.ws> wrote: > > > > > > > > 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. > > > > I was not aware that beadm touches loader.conf, but I find that > slightly horrifying. I won't personally make bectl do that, but I > guess I could at least document that it doesn't... > > > Hi, Today I looked up something for boot environments myself and read this: https://wiki.freebsd.org/BootEnvironments#Setting_Boot_Dataset "In order for boot environments to be effective, you must let the bootfs zpool property control which dataset gets mounted as the root. Particularly, /etc/fstab must be purged of any / mount, and /boot/loader.conf must not be setting vfs.root.mountfrom directly. " So it is documented somewhere at least. Regards, Ronald. ------=_Part_313_1242291649.1661260773941 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body> <p><strong>Van:</strong> Kyle Evans <kevans@freebsd.org><br /> <strong>Datum:</strong> maandag, 22 augustus 2022 17:11<br /> <strong>Aan:</strong> Ronald Klop <ronald-lists@klop.ws><br /> <strong>CC:</strong> Peter Jeremy <peterj@freebsd.org>, freebsd-current@freebsd.org, Ryan Moeller <freqlabs@freebsd.org>, "Patrick M. Hausen" <pmh@hausen.com><br /> <strong>Onderwerp:</strong> Re: Beadm can't create snapshot</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="TextPlainViewer" id="P.P">On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop <ronald-lists@klop.ws> wrote:<br /> ><br /> ><br /> ><br /> > Van: Peter Jeremy <peterj@freebsd.org><br /> > Datum: maandag, 22 augustus 2022 10:45<br /> > Aan: "Patrick M. Hausen" <pmh@hausen.com><br /> > CC: Ryan Moeller <freqlabs@freebsd.org>, freebsd-current@freebsd.org<br /> > Onderwerp: Re: Beadm can't create snapshot<br /> ><br /> > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" <pmh@hausen.com> wrote:<br /> > >Isn't beadm retired in favour of bectl?<br /> ><br /> > bectl still has a number of bugs:<br /> > 1) The output from "bectl list" is in filesystem/bename order rather<br /> > than creation date order. This is an issue if you use (eg) git<br /> > commit hashes as the name.<br /> > 2) "bectl activate" doesn't update /boot/loader.conf so the wrong<br /> > root filesystem is mounted.<br /> ><br /> > That said "bectl create" appears to be a workable replacement for<br /> > "beadm create" and avoids the current "'snapshots_changed' is<br /> > readonly" bugs.<br /> ><br /> > --<br /> > Peter Jeremy<br /> > ________________________________<br /> ><br /> ><br /> ><br /> ><br /> > Hi,<br /> ><br /> > From man bectl:<br /> > activate [-t | -T] beName<br /> > Activate the given beName as the default boot filesystem. If<br /> > the -t flag is given, this takes effect only for the next boot.<br /> > Flag -T removes temporary boot once configuration. Without<br /> > temporary configuration, the next boot will use zfs dataset<br /> > specified in boot pool bootfs property.<br /> ><br /> > 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.<br /> ><br /> <br /> I was not aware that beadm touches loader.conf, but I find that<br /> slightly horrifying. I won't personally make bectl do that, but I<br /> guess I could at least document that it doesn't...</div> <hr /></div> </blockquote> <br /> <br /> Hi,<br /> <br /> Today I looked up something for boot environments myself and read this: https://wiki.freebsd.org/BootEnvironments#Setting_Boot_Dataset<br /> <br /> "In order for boot environments to be effective, you must let the <strong>bootfs</strong> zpool property control which dataset gets mounted as the root. Particularly, <tt>/etc/fstab</tt> must be purged of any / mount, and <tt>/boot/loader.conf</tt> <strong>must not</strong> be setting <tt class="backtick">vfs.root.mountfrom</tt> directly. "<br /> <br /> So it is documented somewhere at least.<br /> <br /> Regards,<br /> <br /> Ronald.<br /> <br /> </body></html> ------=_Part_313_1242291649.1661260773941--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2078216761.314.1661260774009>