Date: Wed, 07 Sep 2011 13:23:30 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, Artem Belevich <art@FreeBSD.org>, =?windows-1252?Q?Martin_Matu=9Aka?= <mm@FreeBSD.org> Subject: Re: "can't load 'kernel'" on ZFS root Message-ID: <4E674622.3040705@FreeBSD.org> In-Reply-To: <20110907094554.GB1674@garage.freebsd.pl> References: <20110907044800.GA96277@server.vk2pj.dyndns.org> <CAFqOu6jv93WKBLMDKPQCOKfOF6Q4zq6PWKQBjSgfWyVvkM4jFw@mail.gmail.com> <4E673751.5080503@FreeBSD.org> <20110907094554.GB1674@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
on 07/09/2011 12:45 Pawel Jakub Dawidek said the following: > The zpool.cache file contains pools that are automatically imported at > system start-up. There might be pools visible in the system that are not > suppose to be automatically imported (eg. a pool on iSCSI disks on > secondary cluster node - importing such pool automatically will corrupt > the data). What about providing a special case for a pool from which we want to boot? Erm, not boot, but to mount a root filesystem. I suppose that we must know name/ID of that pool and if it is not present in zpool.cache, then we could try to find it. Or is this dangerous too? -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E674622.3040705>