Date: Wed, 28 Dec 2016 20:41:51 +0100 From: Dirk-Willem van Gulik <dirkx@webweaving.org> To: FreeBSD Hackers <hackers@freebsd.org> Subject: ZFS and GPT boot - size issue bootblock v.s. default of sysinstall Message-ID: <AB657A06-8886-4EA5-9323-92317707B039@webweaving.org>
next in thread | raw e-mail | index | archive | help
On a default ZFS install (late 2014, 10.x) of a few years hence it seems =
sysinstall selected 64k as the default size of partition 1: with the =
bootblock:
sudo gpart show
=3D> 34 7814037101 ada0 GPT (3.6T)
34 6 - free - (3.0K)
40 128 1 freebsd-boot (64K)
168 67108864 2 freebsd-swap (32G)
67109032 7746928096 3 freebsd-zfs (3.6T)
7814037128 7 - free - (3.5K)
=E2=80=A6. lots of disks snipped =E2=80=A6..
=3D> 34 7814037101 ada35 GPT (3.6T)
34 6 - free - (3.0K)
40 128 1 freebsd-boot (64K)
168 67108864 2 freebsd-swap (32G)
67109032 7746928096 3 freebsd-zfs (3.6T)
7814037128 7 - free - (3.5K)
Fair to assume that this (the 64k) is the reason that from 11.x onwards;=20=
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0=20
fails with an immediate:
gpart: /dev/ada1p1: not enough space=20
as gptzfsboot has grown in recent years to something towards the 90k =
mark ?
-r--r--r-- 1 root wheel 88898 Dec 24 11:52 /boot/gptzfsboot
=09
And I guess avoiding a rebuild would mean something like gently =
disabling swap; shifting partition 1 & 2 carefully an so on ? Or is =
there a more clever way? ZFS has *already* been upgraded.
Or am I missing something ?
Thanks,
Dw=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AB657A06-8886-4EA5-9323-92317707B039>