Date: Tue, 20 Mar 2018 13:10:50 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 Message-ID: <67af9c19-0a42-a435-d922-1e5ce23d1d1c@freebsd.org> In-Reply-To: <888ab314-fb1b-0e08-89d9-0447e7943b76@FreeBSD.org> References: <201803192300.w2JN04fx007127@kx.openedu.org> <alpine.BSF.2.21.1803200759260.66427@mail.fig.ol.no> <888ab314-fb1b-0e08-89d9-0447e7943b76@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-03-20 10:29, Andriy Gapon wrote: > On 20/03/2018 09:09, Trond Endrestøl wrote: >> This step has been big no-no in the past. Never leave your >> bootpool/rootpool in an exported state if you intend to boot from it. >> For all I know, this advice might be superstition for the present >> versions of FreeBSD. > > Yes, it is. That does not matter at all now. > >> From what I can tell from the above, you never created a new >> zpool.cache and copied it to its rightful place. > > For the _rooot_ pool zpool.cache does not matter as well. > It matters only for auto-import of additional pools, if any. > As I mentioned previously, the error reported by the user is before it is even possible to read zpool.cache, so it is definitely not the source of the problem. -- Allan Jude
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67af9c19-0a42-a435-d922-1e5ce23d1d1c>