Date: Sun, 16 Jan 2011 20:07:02 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Marcus =?iso-8859-1?Q?M=FCller?= <znek@mulle-kybernetik.com> Cc: freebsd-fs@freebsd.org Subject: Re: Multiple ZFS pools and booting Message-ID: <20110116190702.GD82886@garage.freebsd.pl> In-Reply-To: <37C1E643-C7A9-4061-8316-281819AC947E@mulle-kybernetik.com> References: <37C1E643-C7A9-4061-8316-281819AC947E@mulle-kybernetik.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 14, 2011 at 02:31:11PM +0100, Marcus M=FCller wrote: > Hi all, >=20 > I have a single harddrive with GPT partitioning: >=20 > root@muller:(~)# gpart show > =3D> 34 234441581 ad10 GPT (112G) > 34 128 1 freebsd-boot (64K) > 162 8388608 2 freebsd-swap (4.0G) > 8388770 10485760 3 freebsd-zfs (5.0G) > 18874530 10485760 4 freebsd-zfs (5.0G) > 29360290 102540662 5 freebsd-zfs (49G) > 131900952 102540662 6 freebsd-zfs (49G) > 234441614 1 - free - (512B) >=20 > ad10p3/ad10p4 (tank) and ad10p5/ad10p6 (muller) are two mirror zpools. Th= e root filesystem currently resides on tank. >=20 > I wanted to migrate the root filesystem from tank to muller by changing t= he mountpoints accordingly and resetting the bootfs zpool propery on tank l= ike this: >=20 > root@muller:(~)# zpool get bootfs muller > NAME PROPERTY VALUE SOURCE > muller bootfs muller/roots/8-current local > root@muller:(~)# zpool set bootfs=3D tank > root@muller:(~)# zpool get bootfs tank > NAME PROPERTY VALUE SOURCE > tank bootfs - default >=20 > But when I reboot, BTX loader tries to access tank:/boot/kernel/kernel. >=20 > Why does the loader care about tank at all, after I "removed" the bootfs = property? > Do I have to export tank before I reboot? > How do I tell the loader to just care about muller for booting? There is no way to configure that at this point. The boot code just boots off of first pool it finds - if there is no bootfs property then it will just try to boot from the top level dataset (ie. tank). What you could try is to add /tank/boot.config file containing: muller:/boot/loader and if that doesn't work: muller/roots/8-current:/boot/loader and if that doesn't work I don't know of any other solutions. Exporting the tank pool will work (for now), but it looks like it will be changed to accept exported pools for booting and skip only destroyed pools. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk0zQdYACgkQForvXbEpPzSuHQCg0vp7WzciuIV/6om3Rbp+ipIH gJ8AoMD2Sj/HkRlJkxhM3r4/vzhqPDPf =idaA -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110116190702.GD82886>