Date: Sat, 17 Feb 2018 19:50:19 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: James Phillips <anti_spam256@yahoo.ca> Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS trashed by bad import Message-ID: <6e6fb440-3db5-ad01-83ca-201e8ae6553a@FreeBSD.org> In-Reply-To: <7336017.290096.1518885201320@mail.yahoo.com> References: <7336017.290096.1518885201320.ref@mail.yahoo.com> <7336017.290096.1518885201320@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/02/2018 18:33, James Phillips wrote: > > -------------------------------------------- > On Sat, 2/17/18, Andriy Gapon <avg@FreeBSD.org> wrote: > > Subject: Re: ZFS trashed by bad import > To: "James Phillips" <anti_spam256@yahoo.ca> > Received: Saturday, February 17, 2018, 2:46 PM > > On 17/02/2018 09:41, James > Phillips via freebsd-fs wrote: > > # zpool import -> > shows list of available pools, including degraded striped > mirror. > > # zpool import -f > 8255478166520290766 granny > > # zpool > status (any zpool command cause same error): > > internal error: failed to > initialize ZFS library > > Not sure if this is what happened, but it looks > like the pool might have a > filesystem with > mountpoint set to / and it got mounted over the real / after > import. > So, you might have a mismatch > between userland and kernel that causes the > further issues. > > I did import by number because the zroot label conflicted. This is not directly related. It's better to import a new pool using -R (altroot) option, so that it does not interfere with the already mounted filesystems and you can examine and modify it. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6e6fb440-3db5-ad01-83ca-201e8ae6553a>