From owner-freebsd-current@FreeBSD.ORG  Mon Oct 12 12:33:18 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 64301106568F;
	Mon, 12 Oct 2009 12:33:18 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 7826F8FC0A;
	Mon, 12 Oct 2009 12:33:17 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA16105;
	Mon, 12 Oct 2009 15:33:15 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Message-ID: <4AD3220B.5030502@icyb.net.ua>
Date: Mon, 12 Oct 2009 15:33:15 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.23 (X11/20090825)
MIME-Version: 1.0
To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 
Subject: zfs boot vs loader
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2009 12:33:18 -0000


I am using ZFS for boot-and-root filesystem. gptzfsboot is used for bootstrapping,
if that matters.
Maybe the following is some kind of a pilot error, but I think that I see a
problem with selecting a different kernel using loader prompt.
That is, I escape to a loader prompt from boot menu. There I do 'unload'. Then I
'load' a different kernel, opensolaris.ko and zfs.ko. Then I 'boot'. Then root
mounting inevitably fails because ZFS root filesystem can not be found.

This is an unexpected result for me.
I wonder if something important for ZFS get unloaded when I unload preloaded
kernel and modules. Perhaps I have to manually re-load zpool.cache?

This happens with recent CURRENT, amd64.
What's strange is that I think that I can switch kernels from loader prompt
without any problems when using RELENG_7 and UFS-boot-plus-ZFS-root approach.

-- 
Andriy Gapon