Date: Mon, 11 Jul 2011 19:47:07 +0200 From: "Christopher J. Ruwe" <cjr@cruwe.de> To: Pan Tsu <inyaoo@gmail.com> Cc: freebsd-fs@freebsd.org, freebsd-questions@freebsd.org Subject: Re: zpool-zfs'es on a GELI-encrypted volume are not mounted at boot [patch included] Message-ID: <20110711194707.48812c43@dijkstra> In-Reply-To: <86tyauc7vb.fsf@gmail.com> References: <20110710142617.1d80289b@dijkstra> <86mxgmjooc.fsf@gmail.com> <20110710160504.0d4bf4c0@dijkstra> <20110710145044.GA94832@icarus.home.lan> <20110710172012.51fce47c@dijkstra> <86tyauc7vb.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Pwder25aXRME1k3orx/=e2r Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 10 Jul 2011 22:23:36 +0400 Pan Tsu <inyaoo@gmail.com> wrote: > "Christopher J. Ruwe" <cjr@cruwe.de> writes: >=20 > [...] > > /etc/rc.d/zvol > > /etc/rc.d/zfs > > /etc/rc.d/dumpon > > /etc/rc.d/ddb > > /etc/rc.d/initrandom > > /etc/rc.d/geli > > /etc/rc.d/gbde > > /etc/rc.d/encswap > > /etc/rc.d/ccd > > /etc/rc.d/swap1 > > /etc/rc.d/fsck > > /etc/rc.d/root > > /etc/rc.d/hostid_save > > /etc/rc.d/mdconfig > > /etc/rc.d/mountcritlocal > > > > This makes sense to me and reflects the order I assumed in my > > description. The question remains, however, if my configuration is > > of any in {unusual, ..., stupid} as I require first zfs mount of /, > > then GELI-unlock and then zfs mount of {/usr,/usr/local, ...}. >=20 > Do you mount the root pool over smth else? Otherwise, root should be > mounted by kernel before init(8) is started. And /etc/rc.d doesn't > exist before root is mounted. I mount root-pool via=20 zfs_load=3D"YES" vfs.root.mountfrom=3D"zfs:rpool/root" in /boot/loader.conf. So far, all is right from what I understand. =20 > I think the correct order is >=20 > 0 vfs_mountroot* > .. > 2 rc.d/zvol (pre v28) > .. > 6 rc.d/geli > .. > 15 rc.d/mountcritlocal > 16 rc.d/zfs >=20 > where extra datasets from the root pool can be mounted via fstab at > rc.d/mountcritlocal time. Not sure if you import geli pool during boot > or not and leak its configuration via zpool.cache. In this setup, I should not have any problems. However, I do not realize (a= nd very much doubt) that I changed anything in the order of the services (l= acking the capability to deterministically do so, anyway). =46rom rcorder I understand that all that is required to set rcorder right wo= uld 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? If so, what could be the reason that my rcorder-setup deviates from the sta= ndard and how could I coerce it back to standard? Thank you for your help so far, cheers --=20 Christopher J. Ruwe TZ GMT + 2 --Sig_/Pwder25aXRME1k3orx/=e2r Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAEBAgAGBQJOGzchAAoJEJTIKW/o3iwUgZwP/jSZ68Bk4xCaxGcsM9+t6TCe 8fUcUqrrxWqpq0QbYd8J5XpKP1GMYtCEqZ9xlg04ycmnQidN8bHiYkADx26cWQbU SoFf9DoPLDSF+8ADC+5VMjHNauq40bErhjAlFQRFsjKrJrueceg/5eD+MCWFT0mn UUwdM7NM/s2rqxKb9VchWeElplBJi+Sl44RIT7R528p6H2/ek9avJOkwwvzfpglI aRIIhxfA7Wmj7DGDh+rClTyKA4DcCMFNXQiA8t7oNkpeMJkWeDOeBmoJcfa0YELl oKTRAoU8PKQLG02H5oxZEamWl08IL8kCC3IaGoPN8gSRBjaZATzJi4QjyFPfz7i3 GcqWqUou8H53vsbUhJRqYBHsVlzS41W1kA4nXkyVitDOVDKVp56tHN6DYkdUgPwe p7F1DqqEMxJ6oBk6RbTIq6bh1ognmKv6vz5+H1HjKPwIDvI+grbTwy1ensrCN281 IaTq0R86g7YumN3//EwOvrFjpmqBFc/T9/XFiTjhRlm1ieMA2iczZ+WcNn6a8NL5 RbjIzKoCGauDNUiEEFFB5sm1KCshXGrl6LaCKbL6MX+3g/L7t8SCQcJVwEZPtagg LM46awwsQjUNPcIISwmEE63HUiLZ6OptIJ2cWbfJ0iH//m2dDUGdzBQIIVdfJhxu LNSNGE67P7FYRe+K5iKR =y8+j -----END PGP SIGNATURE----- --Sig_/Pwder25aXRME1k3orx/=e2r--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110711194707.48812c43>