fsck is failing to clean a filesystem

[Paul Beard]

> On Feb 8, 2016, at 3:37 PM, Polytropon <freebsd at edvax.de> wrote:
> 
> However, the fsck output indicates a quite heavy file system
> inconsistency problem. In worst case, mount -o ro, copy all
> files, re-initialize the filesystem with newfs, and then copy
> the files back. Use tar or rsync or cpio to make sure all the
> file attributes are properly transferred. This should be possible
> in case you cannot resolve the filesystem problem.

That’s the course I’m, creating a new virtual disk to copy everything to. 

> This indicates that the inode entry for "..", the parent directory,
> does not have a valid node type (file, directory, special, link, etc.).
> So fsck doesn't know how to "re-instantiate" this particular ".."
> entry, as it seems.
> 

I couldn’t make sense of the original message or more accurately, what the 
solution might be. Sounds like there isn’t one ;-/