From owner-freebsd-questions@FreeBSD.ORG Mon Nov 7 21:01:21 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8C2B1065673 for ; Mon, 7 Nov 2011 21:01:21 +0000 (UTC) (envelope-from gull@gull.us) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 664AB8FC1E for ; Mon, 7 Nov 2011 21:01:21 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so1893635bkb.13 for ; Mon, 07 Nov 2011 13:01:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.156.208 with SMTP id y16mr19733448bkw.72.1320699680259; Mon, 07 Nov 2011 13:01:20 -0800 (PST) Received: by 10.204.38.195 with HTTP; Mon, 7 Nov 2011 13:01:20 -0800 (PST) X-Originating-IP: [128.95.17.80] In-Reply-To: <4EB67034.2080507@gmx.net> References: <4EB5B512.2000601@gmx.net> <4EB67034.2080507@gmx.net> Date: Mon, 7 Nov 2011 13:01:20 -0800 Message-ID: From: David Brodbeck To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: zfs file names (inodes) without files (ENOENT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2011 21:01:21 -0000 On Sun, Nov 6, 2011 at 3:32 AM, Martin von Gagern wrote: > Makes me wonder whether I'd be better off with either some OpenSolaris > descendant (hoping that the problem only lies in the FreeBSD port of > ZFS) or with Linux (and either btrfs or some more mature fs). Both of those solutions are guaranteed to contain a different set of bugs. ;) I've looked at both FreeBSD and OpenIndiana, and could give you some thoughts on what I see is their respective strong and weak points, if you're interested. It *would* be interesting to see what OpenIndiana made of that filesystem. You could boot a LiveCD and then import the pool and see if you had the same issue. If nothing else that might let you delete the problematic file entry.