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

[Christopher J. Ruwe]

I run my notebook under FreeBSD 8.2-stable,  r223699. I have setup my
disks with ZFS so that I boot from a very small rpool and mount
datasets, among these /usr from another pool configured on top of an
AES encrypted GELI.

When installing a new world using this setup, it is necessary to
manually adapt /etc/rc.d/mountcritlocal, mountcritlocal_start() to do a
zfs mount -a. Failing to do so causes my rootpool to be mounted (which
follows from rc.conf), then the GELI volume to be unlocked. After this,
the boot routine hangs, as /usr (which resides) on the encrypted vol,
which is not mounted, as the canonical zfs mounts are mounted before
GELI. 

I cannot imagine that I am the only one to run ZFSes on an encrypted
GELI volume. Am I booting this setup in an inadvisable way, so that I
need to run into problems? If not, then it might be an idea to
include a zfs mount -a in mountcritlocal in the canonical rc.d-setup.

Am I getting this right or could you please comment?

Thank you, cheers,
-- 
Christopher J. Ruwe
TZ GMT + 2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zfs-mountcritlocal.patch
Type: text/x-patch
Size: 323 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20110705/5dfdebc2/zfs-mountcritlocal.bin