From owner-freebsd-stable@freebsd.org  Sun Dec 18 15:58:45 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CCD6C878F9
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 18 Dec 2016 15:58:45 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from mail.in-addr.com (mail.in-addr.com
 [IPv6:2a01:4f8:191:61e8::2525:2525])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CE011155B
 for <freebsd-stable@freebsd.org>; Sun, 18 Dec 2016 15:58:44 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD))
 (envelope-from <gpalmer@freebsd.org>)
 id 1cIdrG-000P9p-9t; Sun, 18 Dec 2016 15:58:42 +0000
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>
References: <914db6e5-2d8d-15b4-ee96-bc267ce1dbda@davenulle.org>
 <CAKFCL4U=PR_G0zaFf9KX1RKYMZ+PXpZJtDotr84hL_4fhpiAiQ@mail.gmail.com>
 <f23adef2-9fc5-d662-4756-47d660b497c7@davenulle.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f23adef2-9fc5-d662-4756-47d660b497c7@davenulle.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: gpalmer@freebsd.org
X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2016 15:58:45 -0000

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