Re: Beadm can't create snapshot
- In reply to: Peter Jeremy : "Re: Beadm can't create snapshot"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 22 Aug 2022 16:04:37 UTC
On 2022-08-22 12:29, Peter Jeremy wrote: > On 2022-Aug-22 10:56:51 +0200, "Patrick M. Hausen" <pmh@hausen.com> wrote: >>> Am 22.08.2022 um 10:45 schrieb Peter Jeremy <peterj@freebsd.org>: >>> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" <pmh@hausen.com> wrote: >>>> Isn't beadm retired in favour of bectl? >>> >>> 2) "bectl activate" doesn't update /boot/loader.conf so the wrong >>> root filesystem is mounted. >> >> You mean the vfs.root.mountfrom option? I thought that, too, was deprecated and >> replaced by the bootfs property of the zpool. > > I've looking through mailing list archives and searched the 'net and > haven't found anything saying vfs.root.mountfrom is deprecated. > loader(8) mentions that it will fallback to using "currdev" if there's > no root entry in /etc/fstab and vfs.root.mountfrom isn't set. It's not deprecated, but it's a manual override of a _normal_ ZFS boot flow. If you mount root via fstab or you override it via vfs.root.mountfrom, then you should know what you do and why. > At the very least, it's an undocumented incompatibility between beadm > and bectl: I can't take an existing system that's using beadm and just > switch to using bectl. Yeah, but I would blame beadm for doing things in a backwards fashion. -- Andriy Gapon https://standforukraine.com https://razomforukraine.org