Date: Thu, 26 May 2022 12:45:25 +0000 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 Message-ID: <bug-249413-227-wNAPAxaZh7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-249413-227@https.bugs.freebsd.org/bugzilla/> References: <bug-249413-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249413 --- Comment #3 from Anton Saietskii <vsasjason@gmail.com> --- (In reply to cmh from comment #2) > It should simply set canmount as documented (i.e. between noauto and on a= s appropriate) and rely on the normal boottime zfs mounting mechanism. Let's imagine that you have 2 BEs, each with subdataset: zroot/ROOT/default zroot/ROOT/default/var and zroot/ROOT/upgrade zroot/ROOT/upgrade/var Of course, each pair _needs_ to be mounted, but the mountpoints are the sam= e. When you will boot to default, which one var will you get mounted if this w= ill be performed automatically? > Therefore, if I do a zfs list -o name,canmount and see that the dataset i= s set to noauto, I should trust it will not be mounted at boot time. But I totally agree with this. Perhaps using a custom property indicating BEs will be better. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249413-227-wNAPAxaZh7>