Date: Mon, 7 Nov 2011 13:01:20 -0800 From: David Brodbeck <gull@gull.us> To: freebsd-questions@freebsd.org Subject: Re: zfs file names (inodes) without files (ENOENT) Message-ID: <CAHhngE2xXU_apC2=ockAH38s54NuAQQq47sbTg1DCfVs8awrtA@mail.gmail.com> In-Reply-To: <4EB67034.2080507@gmx.net> References: <4EB5B512.2000601@gmx.net> <4EB67034.2080507@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 6, 2011 at 3:32 AM, Martin von Gagern <Martin.vGagern@gmx.net> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHhngE2xXU_apC2=ockAH38s54NuAQQq47sbTg1DCfVs8awrtA>