From owner-freebsd-sysinstall@FreeBSD.ORG Sat Mar 22 15:03:16 2014 Return-Path: Delivered-To: sysinstall@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F289104 for ; Sat, 22 Mar 2014 15:03:16 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1134B6D9 for ; Sat, 22 Mar 2014 15:03:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2MF3FG3042528 for ; Sat, 22 Mar 2014 15:03:15 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2MF3FXf042525 for sysinstall@FreeBSD.org; Sat, 22 Mar 2014 15:03:15 GMT (envelope-from bdrewery) Received: (qmail 51098 invoked from network); 22 Mar 2014 10:03:14 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 22 Mar 2014 10:03:14 -0500 Message-ID: <532DA62A.7020106@FreeBSD.org> Date: Sat, 22 Mar 2014 10:03:06 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: dteske@FreeBSD.org Subject: Re: bsdinstall ZFS /root in wrong dataset References: <532D84AF.5080506@FreeBSD.org> <010101cf45de$c9707380$5c515a80$@FreeBSD.org> In-Reply-To: <010101cf45de$c9707380$5c515a80$@FreeBSD.org> X-Enigmail-Version: 1.6 OpenPGP: id=6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="U8FFt1FCQs9qem5cttujVxCwcJiuJr1r7" Cc: sysinstall@FreeBSD.org X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2014 15:03:16 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --U8FFt1FCQs9qem5cttujVxCwcJiuJr1r7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 3/22/2014 9:55 AM, dteske@FreeBSD.org wrote: >> -----Original Message----- >> From: Bryan Drewery [mailto:bdrewery@FreeBSD.org] >> Sent: Saturday, March 22, 2014 5:40 AM >> To: sysinstall@FreeBSD.org >> Subject: bsdinstall ZFS /root in wrong dataset >> >> (I am not subscribed so please CC me) >> >> The ZFS layout uses the zroot/ROOT/ to support boot environments. >> The problem with it is that /root is part of the BE. Home directories = are >> properly outside of the BE. >> >> /root should really be outside to persist history and other changes to= > root's >> homedir through BE changes/upgrades. >> >> This is quite noticeable if you create a new BE (beadm create; beadm >> mount) and then installworld/kernel into it, then activate and reboot.= >> All of your history and /root changes are missing for the period betwe= en >> creating the BE and rebooting. >> >> Something like this is needed: >> >>> --- usr.sbin/bsdinstall/scripts/zfsboot (revision 263620) >>> +++ usr.sbin/bsdinstall/scripts/zfsboot (working copy) >>> @@ -128,6 +128,8 @@ >>> >>> # Home directories separated so they are common to all BEs >>> /usr/home # NB: /home is a symlink to /usr/home >>> + /root mountpoint=3D/root >>> >>> # Ports tree >>> /usr/ports compression=3Dlz4,setuid=3Doff >> >> >> Though, I am unsure on whether we should make a zroot/root dataset and= >> mount it in or mkdir /usr/home/root and symlink /root to it. The symli= nk >> does cause mergemaster confusion though. I have no opinion on where we= >> create the root dataset, as long as it is outside of ROOT. >> >=20 > Hi bdrewery, >=20 > Thanks for kicking off this thread (esp. on list). >=20 > Placing /root in /usr/home/root would break in a few scenarios as you > correctly identified. Let's give your patch a go and wait for some feed= back > before MFC'ing. I don't expect any fallout from your patch; looks great= > and indeed should solve the problem (if I understand correctly). >=20 > Do you want to commit or should I? >=20 Sounds good. I'll commit in about an hour. --=20 Regards, Bryan Drewery --U8FFt1FCQs9qem5cttujVxCwcJiuJr1r7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTLaYqAAoJEDXXcbtuRpfPvw8IANgQxb/WxasB3pSUHV2ofOei G/HUU5n5S/+JAHJfrfryGulXOYsA9Sp4Yrj3egZ/lAF8mWnBcFA8f86Wwl6G02LQ H5Va3s9FdSGrioUP5aS7CX5MJWRLlFI8piXku5W0FB5pYoQJGto+bcaerQP1BqmT eAk3uS7kt3VqKL9eqDg8LVJbwRmJv/iNRQRovI6iIt202DEOf27kJ/dkXEjMr7WB pGzjkV3gT8BK7gS+A0IQgSbPRUFbOnLZ+V58cDsi+kX93GbgFzZaGMwdumbRUrP3 bpdauX3T30VG/RcI9YjPQFSY8I233Q2OdxMl/vF+ndrm/eNzBZl/VX3GWqHHldA= =oNeV -----END PGP SIGNATURE----- --U8FFt1FCQs9qem5cttujVxCwcJiuJr1r7--