zpool-zfs'es on a GELI-encrypted volume are not mounted at boot
Christopher J. Ruwe
cjr at cruwe.de
Fri Jul 22 15:25:01 UTC 2011
On Tue, 12 Jul 2011 00:25:38 +0400
Pan Tsu <inyaoo at gmail.com> wrote:
> "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
> $ 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.
Please accept my apologies for replying so late, I was stuck up in work and could not find time to test this issue.
Your proposed solution of reverting to the default setup worked as expected. My idea of adding a REQUIRE: geli to /etc/rc.d/zfs did not, although rcorder showed geli before zfs then.
However, with my problem solved, I have no incentive to research why I deviated from default rc.d in the first place ... the only thing I am sure of is, that it was not intentionally.
Anyhow, thank you for your help, it is really appreciated.
Christopher J. Ruwe
TZ GMT + 2
More information about the freebsd-questions