zpool-zfs'es on a GELI-encrypted volume are not mounted at boot [patch included]

Pan Tsu inyaoo at gmail.com
Mon Jul 11 20:26:03 UTC 2011

"Christopher J. Ruwe" <cjr at cruwe.de> writes:

> In this setup, I should not have any problems. However, I do not
> realize (and very much doubt) that I changed anything in the order of
> the services (lacking the capability to deterministically do so,
> anyway).
> From rcorder I understand that all that is required to set rcorder
> right would be to change /etc/rc.d/zfs to include a REQUIRE: geli, so
> that my geli-encrypted volume would be unlocked before all
> zfs-datasets are mounted?

Yep, or revert to default where rc.d/zfs depends on rc.d/mountcritlocal.

  $ svn co -qr223699 svn://svn.freebsd.org/base/stable/8/etc/rc.d
  $ rcorder rc.d/* | nl | sed /zfs/q
       1  rc.d/hostid
       2  rc.d/zvol
       3  rc.d/dumpon
       4  rc.d/ddb
       5  rc.d/initrandom
       6  rc.d/geli
       7  rc.d/gbde
       8  rc.d/encswap
       9  rc.d/ccd
      10  rc.d/swap1
      11  rc.d/fsck
      12  rc.d/root
      13  rc.d/hostid_save
      14  rc.d/mdconfig
      15  rc.d/mountcritlocal
      16  rc.d/zfs
> If so, what could be the reason that my rcorder-setup deviates from
> the standard and how could I coerce it back to standard?

No idea. Try basic check with

  $ diff -ur /usr/src/etc/rc.d /etc/rc.d
  $ mergemaster
  $ mergemaster -s

unless someone else can reproduce your issue.

More information about the freebsd-questions mailing list