[Bug 214911] bsdinstall/scripts/zfsboot detaches *all* GELI devices

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Nov 28 17:39:10 UTC 2016


            Bug ID: 214911
           Summary: bsdinstall/scripts/zfsboot detaches *all* GELI devices
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: freebsd at tim.thechases.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Attempting to create a `md0` drive image to upload to my hosting service, I'm
using `bsdinstall` to try and do the install. This worked in 10.3, but changes
in 11 trigger issues.  To repeat, issue the following on an existing 11.0
system installed on a ZFS-on-GELI configuration:

    ## show the current system is on GELI
    # geli list | grep Name
    Name: ada0p4.eli
    Name: ada0p4
    Name: ada0p3.eli
    Name: ada0p3

    ## show that ada0p4.eli is the only backing member of zroot
    # zpool status zroot
        NAME          STATE     READ WRITE CKSUM
        zroot         ONLINE       0     0     0
          ada0p4.eli  ONLINE       0     0     0

    ## create a 10GB disk image file
    dd if=/dev/zero of=freebsd.img bs=10m count=1k

    ##turn it into a disk
    # mdconfig -f freebsd.img -u 0

    ## run bsdinstall
    # bsdinstall

Specify guided ZFS-on-root, a single stripe backed by `md0` and encrypt both
the pool and the swap.  Proceeding with install the will show messages on the
console that *ada0p4.eli* has been detached and the host machine will hang for
the obvious reason that its underlying GEOM_ELI has been forcibly detached and
there's no longer any root file-system.

Digging further shows that /usr/src/usr.sbin/bsdinstall/scripts/zfsboot is
forcibly detaching *all* GELI providers (around line 793, using GELI_DETACH_F),
not just those that it created during the install process.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the freebsd-amd64 mailing list