From owner-freebsd-stable@freebsd.org Thu Apr 28 12:03:36 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB25CB1D040 for ; Thu, 28 Apr 2016 12:03:36 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8536F1D34 for ; Thu, 28 Apr 2016 12:03:36 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (123-48-23-227.dz.commufa.jp [123.48.23.227]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id u3SC3XJk085830 for ; Thu, 28 Apr 2016 21:03:34 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 28 Apr 2016 21:03:33 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Subject: Re: booting from separate zfs pool Message-Id: <20160428210333.0d446772c3093aad688fffd0@dec.sakura.ne.jp> In-Reply-To: <20160428203951.4530ea15eab5071b18a55708@dec.sakura.ne.jp> References: <5721BF5C.1070201@norma.perm.ru> <20160428093104.GF26740@phobos.mjch.net> <039f3785-2710-baeb-7cb9-91dcac2b2be3@multiplay.co.uk> <20160428203951.4530ea15eab5071b18a55708@dec.sakura.ne.jp> Organization: Junchoon corps X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 12:03:36 -0000 And with this feature, if I understood correctly, old kernel keeps on running after this type of reboot. If so, kernel modules loaded via /etc/rc.conf[.local] can cause version mismatch with running kernel, forcing single user mode. So I'd prefer making 'zboot' pool as real rootfs and mount needed datasets from main pool. (Use povot-root only for userland-only updates.) # Pivot-root would be similar to configuration below. Right? *Use UEFI loader of 10.3 or later *UFS having /boot *ZFS NOT having /boot (at least, /boot/loader.efi) */boot/loader.conf has vfs.root.mountfrom line pointing inside ZFS Below can be optional. *UFS is mounted to some mountpoint such as /ufsboot after boot *ZFS has symlink /boot pointing /ufsboot On Thu, 28 Apr 2016 20:39:51 +0900 Tomoaki AOKI wrote: > Finished at r293744 (MFC of r290548), right? > > https://lists.freebsd.org/pipermail/svn-src-stable-10/2016-January/007753.html > > > On Thu, 28 Apr 2016 11:57:44 +0100 > Steven Hartland wrote: > > > I thought that was in 10.3 as well? > > > > > > On 28/04/2016 11:55, krad wrote: > > > I think the new pivotroot type stuff in 11 may help a lot with this > > > > > > https://www.freebsd.org/news/status/report-2015-10-2015-12.html#Root-Remount > > > > > > > > > > > > On 28 April 2016 at 10:31, Malcolm Herbert wrote: > > > > > >> On Thu, Apr 28, 2016 at 12:44:28PM +0500, Eugene M. Zheganin wrote: > > >> |So, I'm still struggling with my problem when I cannot boot from a big > > >> |zfs 2T pool (I have written some messages about a year ago, the whole > > >> |story is too long and irrelevant to retell it, I'll only notice that I > > >> |took the path where I'm about to boot from a separate zfs pool closer to > > >> |the beginning of the disk). > > >> > > >> it's no an answer to your question, but I'm wondering wether the solution > > >> to this may also help with beadm being unable to work with crypted ZFS root > > >> volumes as the boot zpool is not the same as zroot ... I've got that issue > > >> myself ... > > >> > > >> -- > > >> Malcolm Herbert > > >> mjch@mjch.net > > >> _______________________________________________ > > >> freebsd-stable@freebsd.org mailing list > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > >> > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > -- > Tomoaki AOKI junchoon@dec.sakura.ne.jp > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Tomoaki AOKI junchoon@dec.sakura.ne.jp