From nobody Mon Aug 22 16:04:37 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 4MBHHc4JNCz4Z1f7 for ; Mon, 22 Aug 2022 16:04:44 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MBHHb2pQ8z3N7h; Mon, 22 Aug 2022 16:04:43 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: (Authenticated sender: andriy.gapon@uabsd.com) by mail.gandi.net (Postfix) with ESMTPSA id 9A4ABFF808; Mon, 22 Aug 2022 16:04:40 +0000 (UTC) Message-ID: <05974a7f-ec80-3ab0-c09b-2a222148e4a2@FreeBSD.org> Date: Mon, 22 Aug 2022 19:04:37 +0300 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.1.2 Subject: Re: Beadm can't create snapshot Content-Language: en-US To: Peter Jeremy , "Patrick M. Hausen" Cc: Ryan Moeller , freebsd-current@freebsd.org References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> <1E09DD0A-9F26-4BAD-9CA4-B3593B2DE836@hausen.com> From: Andriy Gapon In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4MBHHb2pQ8z3N7h X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 217.70.183.199 is neither permitted nor denied by domain of avg@FreeBSD.org) smtp.mailfrom=avg@FreeBSD.org X-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[217.70.183.199:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:29169, ipnet:217.70.176.0/20, country:FR]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[217.70.183.199:from]; R_SPF_SOFTFAIL(0.00)[~all:c]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[avg]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; ARC_NA(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 2022-08-22 12:29, Peter Jeremy wrote: > On 2022-Aug-22 10:56:51 +0200, "Patrick M. Hausen" wrote: >>> Am 22.08.2022 um 10:45 schrieb Peter Jeremy : >>> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" 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