Re: 14.3 R zfs canmount options for pool/ROOT/default from on to noauto

On 6/11/2025 2:27 PM, mike tancsa wrote:
> Hi all,
>
> One of my image generation scripts got tripped up over this today as I 
> was trying to use 14.3R as the base from 14.2.  Any idea why from 14.2 
> to 14.3 the pool defaults went from
>
>
> zroot/ROOT/default  canmount on                        default
>
> to
>
> zroot/ROOT/default  canmount              noauto 
>                        default
>
>
> Curious as to why it got changed.  When I do freebsd-update upgrade -r 
> 14.3 from images that started out as 14.1 it doesnt change the value 
> for existing pools and am not sure if something in userland like bectl 
> depend on the flag being so set to noauto now. Any insights ?
>
>
This seems to be the commit

commit 636d377264f51e3dd33bd7f33ebf03e2e148d40d
Author: Kyle Evans <kevans@FreeBSD.org>
Date:   Tue Dec 10 19:19:08 2024 -0600

     release: vmimage: setup the default BE properly

     All of the BE datasets need to be set canmount=noauto so that creating
     a new BE and switching to it can actually work.  With the current 
setup,
     the zfs rc script will mount the `default` BE over whichever new BE is
     activated once it runs.

     Reported by:    andrew
     Reviewed by:    andrew, re (cperciva), imp, markj
     Differential Revision:  https://reviews.freebsd.org/D48017


My script was failing because
zpool import -f -R ${TARGETMOUNT} ${BASEPOOLNAME}  ${NAME}

assumed / was mounted when I did the import.   I have worked around it 
for now

     ---Mike