From owner-freebsd-fs@FreeBSD.ORG Fri Oct 5 17:43:52 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78F90106566B for ; Fri, 5 Oct 2012 17:43:52 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C26B58FC0C for ; Fri, 5 Oct 2012 17:43:51 +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 UAA01260; Fri, 05 Oct 2012 20:43:48 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <506F1C54.1060109@FreeBSD.org> Date: Fri, 05 Oct 2012 20:43:48 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: "Matthew D. Fuller" References: <505DE715.8020806@FreeBSD.org> <506C50F1.40805@FreeBSD.org> <20121005063848.GC1389@garage.freebsd.pl> <20121005174223.GU71113@over-yonder.net> In-Reply-To: <20121005174223.GU71113@over-yonder.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs: allow to mount root from a pool not in zpool.cache X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2012 17:43:52 -0000 on 05/10/2012 20:42 Matthew D. Fuller said the following: > On Fri, Oct 05, 2012 at 08:38:49AM +0200 I heard the voice of > Pawel Jakub Dawidek, and lo! it spake thus: >> >> In my opinion requiring no zpool.cache to import root pool and mount >> root file system is great idea and we should definiately do it. > > As a user, I heartily agree. I've setup a number of ZFS systems now, > generally by booting up a live CD/USB/existing install on an extra > drive, setting up and installing files, then unplugging the temp drive > and letting it come up. > > So far, I haven't yet _ever_ had it actually boot right the first > time. It keeps getting up to the root mount and failing. I've always > had to plug the other drive back in and "squirrel around" with > zpool.cache until it works. The last time, I believe it was because > during the setup I had one NIC plugged in, and the "real" system used > the other, so the hostid wound up different? It's kinda like an > adventure game, but the replay value is a bit low 8-} So try the patch from the start of this thread :-) It may to get it committed. -- Andriy Gapon