From owner-freebsd-fs@freebsd.org  Wed Apr 13 13:12:56 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 6A67BB0F37D
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 13 Apr 2016 13:12:56 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 5B364172A
 for <freebsd-fs@FreeBSD.org>; Wed, 13 Apr 2016 13:12:56 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3DDCu6i045822
 for <freebsd-fs@FreeBSD.org>; Wed, 13 Apr 2016 13:12:56 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 208742] /boot/gptzfsboot boots kernel from another zpool (not
 root pool)
Date: Wed, 13 Apr 2016 13:12:56 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-208742-3630-u9E8gTkOcq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208742-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-208742-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 13:12:56 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208742

--- Comment #9 from Andriy Gapon <avg@FreeBSD.org> ---
(In reply to Steven Hartland from comment #3)
We have some control via /boot.config or /boot/config, but they have to be
placed on the first pool.  BTW, I am not sure if just removing zfsloader fr=
om
the first pool is going to help. I suspect that that can result in a boot
failure, but I am not sure.

There has also been a proposal for the ZFS boot chain to ignore pools that =
do
not have bootfs explicitly set unless such a pool is an only discovered poo=
l.
I think that that makes sense.

--=20
You are receiving this mail because:
You are the assignee for the bug.=