Date: Sun, 18 Dec 2016 15:58:42 +0000 From: Gary Palmer <gpalmer@freebsd.org> To: David Marec <david.marec@davenulle.org> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: [ZFS] files in a weird situtation Message-ID: <20161218155842.GD7032@in-addr.com> In-Reply-To: <f23adef2-9fc5-d662-4756-47d660b497c7@davenulle.org> References: <914db6e5-2d8d-15b4-ee96-bc267ce1dbda@davenulle.org> <CAKFCL4U=PR_G0zaFf9KX1RKYMZ%2BPXpZJtDotr84hL_4fhpiAiQ@mail.gmail.com> <f23adef2-9fc5-d662-4756-47d660b497c7@davenulle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 17, 2016 at 11:25:41PM +0100, David Marec wrote: > On 17.12.2016 22:15, Brandon Allbery wrote: > > > > You have a directory entry pointing at a freed inode (or zfs equivalent). > > ZFS may have mapped this inode that points to nowhere. That makes sense. > > In this case, what should be the best solution to clean this up ? > > As I said, as far scrubbing the pool didn't show any error, it didn't > solve the issue. Have you tried deleting the /lib directory, or at least renaming it to /lib.bad (or something similar)? You'll need to boot from a rescue disc or boot single user with /rescue/sh as your shell, and then reinstall /lib from known good media (or "make installworld" in /usr/src) That may leave problems in the ZFS metadata still, but it should (in theory) let you continue using the system Gary P.S. I haven't tried any of this myself so be careful
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161218155842.GD7032>