It looks like an inode became corrupt. How this happened I don't know, but probably the easiest solution in this particular case is to use the 'hammer2' utility to destroy the inode and to delete the bad directory entry (man hammer2), then run a few hammer2 bulkfree passes and see if that cleans it up.
Usually when a H2 filesystem becomes corrupt it points to some other issue in the system. This being a VM, there could be any number of potential issues causing the corruption but I don't have any ideas as to what it was in this case. It is usually best to copy the data off and reformat after such events. -Matt
