From owner-freebsd-bugs@freebsd.org Thu Sep 17 23:58:13 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 36EB93F15D8 for ; Thu, 17 Sep 2020 23:58:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4Bsv6s0flHz3ZTy for ; Thu, 17 Sep 2020 23:58:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 166243F16DC; Thu, 17 Sep 2020 23:58:13 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 162143F1A9A for ; Thu, 17 Sep 2020 23:58:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bsv6r6Zbbz3ZKS for ; Thu, 17 Sep 2020 23:58:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A6ECF121B4 for ; Thu, 17 Sep 2020 23:58:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 08HNwCGW001450 for ; Thu, 17 Sep 2020 23:58:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 08HNwCvu001446 for bugs@FreeBSD.org; Thu, 17 Sep 2020 23:58:12 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 249413] bectl - should manipulate canmount on child datasets of the root instead of relying on /etc/rc.d/zfsbe Date: Thu, 17 Sep 2020 23:58:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.4-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: freebsd@juicer.orange-carb.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2020 23:58:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249413 Bug ID: 249413 Summary: bectl - should manipulate canmount on child datasets of the root instead of relying on /etc/rc.d/zfsbe Product: Base System Version: 11.4-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: freebsd@juicer.orange-carb.org bectl uses a counterintuitive and confusing approach to mounting child data= sets of the root in boot environments. The current approach sets all boot environment datasets to canmount=3Dnoaut= o and relies on /etc/rc.d/zfsbe to mount individual child datasets.=20 This works, but is unnecessarily opaque and results in unexpected behaviour relative to the normal expectation of zfs filesystem mounting. In addition,= the approach requires a specific naming scheme for child datasets (see comments= in /etc/rc.d/zfsbe) that appears unnecessary and is undocumented from the perspective of a user trying to use the provided tools without detailed knowledge of the scheme. I suggest that bectl be modified to set the zfs canmount=3Don property on t= he root dataset and all child datasets when activating a boot environment, and= set the zfs canmount=3Dnoauto property on the root and child datasets of the bo= ot environment that is deactivated. In this arrangement there would be no need= for magic behaviour from /etc/rc.d/zfsbe at boot time. In addition, the current behaviour for child datasets is undocumented in the bectl manpage (which is quite terse) as is the naming scheme requirements in /etc/rc.d/zfsbe. Regardless of the outcome of this bug, bectl needs additio= nal documentation on child datasets of the root, as the process is not fully explained. For example, the significance of the -r flag on 'bectl create' n= eeds to be explained in the context of child datasets of the root. The discussion at the following forum thread may also be helpful. https://forums.freebsd.org/threads/boot-environments-child-datasets-not-act= ivating.77002/ --=20 You are receiving this mail because: You are the assignee for the bug.=