Date: Fri, 05 Oct 2012 20:43:48 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs: allow to mount root from a pool not in zpool.cache Message-ID: <506F1C54.1060109@FreeBSD.org> In-Reply-To: <20121005174223.GU71113@over-yonder.net> References: <505DE715.8020806@FreeBSD.org> <DA42C8E9-BFFF-4C5A-9E14-1D50EAEFA669@scsiguy.com> <506C50F1.40805@FreeBSD.org> <20121005063848.GC1389@garage.freebsd.pl> <20121005174223.GU71113@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?506F1C54.1060109>