Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 May 2016 22:15:11 +0200
From:      =?UTF-8?Q?Ren=c3=a9_Ladan?= <rene@freebsd.org>
To:        Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: ZFS on root, beadm, and the /boot symlink
Message-ID:  <77cd8159-a476-4284-7fa5-2daae2ecf67f@freebsd.org>
In-Reply-To: <6ff9950d-2b43-4799-9812-46e081d2b72b@freebsd.org>
References:  <20160522184113.GU19887@gmail.com> <6ff9950d-2b43-4799-9812-46e081d2b72b@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--IPkumnChpd2D9akAkrRAgLCP4k1vGBtv8
Content-Type: multipart/mixed; boundary="lhCDXeksPQHFk4IuutsVnnXmemOXHDf2q"
From: =?UTF-8?Q?Ren=c3=a9_Ladan?= <rene@freebsd.org>
To: Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org
Message-ID: <77cd8159-a476-4284-7fa5-2daae2ecf67f@freebsd.org>
Subject: Re: ZFS on root, beadm, and the /boot symlink
References: <20160522184113.GU19887@gmail.com>
 <6ff9950d-2b43-4799-9812-46e081d2b72b@freebsd.org>
In-Reply-To: <6ff9950d-2b43-4799-9812-46e081d2b72b@freebsd.org>

--lhCDXeksPQHFk4IuutsVnnXmemOXHDf2q
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 05/22/16 21:11, Allan Jude wrote:
> On 2016-05-22 14:41, Randy Westlund wrote:
>> My system was installed from 10.1 or 10.2 with root on ZFS and geli, b=
ut
>> now it tracks current.  It is not an EFI system.  I'm trying to get bo=
ot
>> environments to work, but the /boot symlink is throwing me off.
>>
>> I have two pools from the installer's layout; a small bootpool and
>> zroot.  The bootpool mounts at /bootpool and /boot is a symlink to it.=

>>
>>> randy@mako /> zfs get mountpoint bootpool
>>> NAME      PROPERTY    VALUE       SOURCE
>>> bootpool  mountpoint  /bootpool   local
>>>
>>> randy@mako /> ls -al /boot
>>> lrwxr-xr-x  1 root  wheel  13 Aug 12  2015 /boot -> bootpool/boot
>>
>> When I try to activate a boot environment, I get this error:
>>
>>> root@mako:/ # beadm activate r300358
>>> cp: /tmp/BE-r300358.FS6Xo6ot/boot/zfs/zpool.cache: No such file or di=
rectory
>>
>> Because the new boot environment has a symlink to an empty directory:
>>
>>> randy@mako /> ls -al /tmp/BE-r300358.FS6Xo6ot/boot
>>> lrwxr-xr-x  1 root  wheel  13 Aug 12  2015 /tmp/BE-r300358.FS6Xo6ot/b=
oot -> bootpool/boot
>>>
>>> randy@mako /> ls -al /tmp/BE-r300358.FS6Xo6ot/bootpool
>>> total 9
>>> drwxr-xr-x   2 root  wheel   2 Aug 18  2015 .
>>> drwxr-xr-x  21 root  wheel  29 May 21 16:23 ..
>>
>> Mergemaster complains about the /boot symlink as well.
>>
>> I'm not sure what the cachefile does or why it's there.  It has a rece=
nt
>> modification time, but neither pool seems to reference it.
>>
>>> randy@mako /> zpool get cachefile zroot
>>> NAME   PROPERTY   VALUE      SOURCE
>>> zroot  cachefile  -          default
>>
>>> randy@mako /> zpool get cachefile bootpool
>>> NAME      PROPERTY   VALUE      SOURCE
>>> bootpool  cachefile  -          default
>>
>>> randy@mako /> ls -al /boot/zfs/zpool.cache
>>> -rw-r--r--  1 root  wheel  2512 May 21 16:23 /boot/zfs/zpool.cache
>>
>> What's the proper way to handle the /boot symlink with beadm?
>>
>> Randy
>>
>=20
> It is not possible to use boot environments when you have a separate
> bootpool. This is the motivation for my recent work to implement GELI i=
n
> boot2 and loader, to allow you to combine GELI encryption with ZFS boot=

> environments, which previously required a second unencrypted pool for
> the loader and kernel.
>=20
Ah, I ran into this as well. I installed FreeBSD in UEFI mode from
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ which
creates a separate boot pool as described above.

Although creating the new boot environment went fine, upgrading that to
a pkgbase install with the new boot environment jailed failed when
installing the FreeBSD-runtime package because that installs
/boot/loader.efi and /boot is a dangling symbolic link in that jail.

Regards,
Ren=E9



--lhCDXeksPQHFk4IuutsVnnXmemOXHDf2q--

--IPkumnChpd2D9akAkrRAgLCP4k1vGBtv8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJXQhNPXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMDFBNzE2QjE2MkIwMEU1NUJFREVBMDVB
REJCRjg2MTBBMzc4OUI3AAoJEK27+GEKN4m3up8QAI5DlPlSoATQ74mkM0fUtQLl
MxnEHxRpR//9qJ1+Vra4eG3ie5BzhfItFdb8oFRI2LFiiAJGX1rwVxrziRoqK3nH
YQxn3R8a1i4ljPEPxAmY1LuhI94EdeFvUAOiAi/bFFLfHbkd7qF++OqGz7OgISOn
Wx8aRf3QjnTw8AiPbD381fVRIPJS0ggBwFvjhmWi+zQ2bCtY2/fyj243wGvVFCuI
LJd4NDS6vdQ30gSMmoJXOxzyTVy2f00m0vVpbo9OmShSFOTFuSds5j5uTFawj8TV
xXmz0OhCdxmA3fEnTGnnvS/0UsN8NPnE3VCgFnzzVbbTUAeRFRYucr8OHEcVmYmn
JgTS4MfBa17zcygviqq/uxAjVcf4FjpwkpPhRswKbAN9BgkeSsPomw4Y0LM9aqre
Vq/xPuZ1DMj9/f0DrlZXJAXFMpZ5l/pqJup3IGeJIS3OTq7hUNfoQ8IpzNtkcq4/
kXYH/rkjfakDz/9Hx6zO4uNOINa0H299m+HI+lm/HaxxPoY3YFfI+EojM6TzCO40
IAkZyCVMBTsxSK7wtDbU9j2oGnOuFXQV1hBI8qiw2q11l7EneHiu0MXfSHTUXtar
37iSTi/W3Y6bPWHwYxWSNMQ9pnws1ebewi2tfLfVbYoM0M8XBf+ybBPonOJuUY5j
ya6m+hkDNcZ1GbnBgXAc
=qlln
-----END PGP SIGNATURE-----

--IPkumnChpd2D9akAkrRAgLCP4k1vGBtv8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77cd8159-a476-4284-7fa5-2daae2ecf67f>