Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Jul 2011 16:05:04 +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:  <20110710160504.0d4bf4c0@dijkstra>
In-Reply-To: <86mxgmjooc.fsf@gmail.com>
References:  <20110710142617.1d80289b@dijkstra> <86mxgmjooc.fsf@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/g_=5Uw8m_5L.Z.3xp0eX_.p
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sun, 10 Jul 2011 16:38:43 +0400
Pan Tsu <inyaoo@gmail.com> wrote:

> "Christopher J. Ruwe" <cjr@cruwe.de> writes:
>=20
> > Nearly a week ago I posted this question to freebsd-fs, but
> > probalby my question is a) worded too complicatedly, b) not really a
> > filesystem-issue or c) both.
> >
> > To rephrase: In setups requiring one or more ZFS-dataset to be
> > mounted before another service is activated (GELI in my case) and
> > the rest of the ZFS-datasets after that service is activated
> > (because they require GELI), it seems to be necessary to add a `zfs
> > mount -a` to mountcritlocal. Is this considered correct behaviour
> > and wouldn't it make sense to add such a line to mountcritlocal in
> > the standard setup?
> [...]
>=20
> Have you tried to set zfs_enable=3DYES in rc.conf? Based on rcorder(8)
> output rc.d/zfs should come just after rc.d/mountcritlocal.

zfs_enable=3D"YES" is set. rcorder gives curious output, so maybe my etcs a=
re wrong?

$> rcorder /etc/rc.d/zfs
rcorder: file `/etc/rc.d/zfs' is before unknown provision `mountlate'
/etc/rc.d/zfs

$> rcorder /etc/rc.d/mountcritlocal
rcorder: requirement `root' in file `/etc/rc.d/mountcritlocal' has no provi=
ders.
/etc/rc.d/mountcritlocal

However, I fear I have not made my intent clear. My boot-sequence should be=
 as follows (intermittent steps left out):

1) mount zfs root-fs, which is on plain standard zpool A
2) unlock another, GELI-encrypted zpool B
3) mount all other fs (/usr,...), which reside on zpool B

What my system does is first to mount the fs on zpool A, then GELI-unlock a=
nd then halt because the contents of /usr are not accessible (yet)

What I want my system to do is to first  mount root, then unlock GELI and t=
hen mount all other remaining fs on zpool B.

I could either mount all remaining zfs'es in mountcritlocal, which
requires another line there, which I have added locally as put in my
patch. I cannot shift the order so that GELI-unlock comes first, because
my keys for GELI reside on /boot, which resides on zpool A.

So, is my setup anything from unfortunate to plain stupid or is
mountcritlocal missing a statement catering for such cases as I
described?

Thank you for your help, cheers,
--=20
Christopher J. Ruwe
TZ GMT + 2

--Sig_/g_=5Uw8m_5L.Z.3xp0eX_.p
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)

iQIcBAEBAgAGBQJOGbGVAAoJEJTIKW/o3iwUPjQQANILgykncBQ0VL85din/a3HY
veGlmpfVWM2I+lebeOwLEU3EJx93+T8mMbEQp0btz7J1Jd8Guf+2BeBJ1IZMkIYC
qR/foBnBH5LQYUP8BLjozXB9Y2KgmekTDqQqTImUuDMXOlfi0HGQatGviUYRB3fy
zjohMsK42VIQtG1x9UAkDpCe8K5NkFB2OrQ6zGVYiIoT68O89C/skKCa2g4KL4bi
+QeaG5ShqeRNiiowPUsaTW0PVXuscg2r0GTKD6Y0ZWzwEAhm0pSojR9W6IshwTws
59hlHYjv0TeiYRDhuTP8nhSpkmVWAO4qqyPh0cSsvd3Ot8M7drIwIzeivAA81x98
J88K70rP/QWBCbpwsZcPFAIIQdURBvgn6T7OiTm0nDzWr2+JX+RjNVj3FPehxCNA
xAEvREkEFb61jPkTue6Bb4HC47aAkhpowgegWFUdRGskRhmpFjZ+hnht6oL9a1xp
nEf+mxnieL3eCa5U/4RtuX2ZtciBOuL9/Se/1Zk+nwsKGAnZsu7we8pNYrqysBER
eUpX6yqERUWW2yLHPYbvQYFw4GeJwId7jf9bm+xx7dR5nFGJ5/lgsLCLKAEP4zVQ
vQnAI3dHYawrz1+Dshh5XLWnk9dYnbJOr2jZuuXc7KkKydG8I/oNmLj5yLP+79g0
iNuDBw6DepWIDELEKVUL
=bSSb
-----END PGP SIGNATURE-----

--Sig_/g_=5Uw8m_5L.Z.3xp0eX_.p--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110710160504.0d4bf4c0>