The relevant error messages are: unable to find ref byte errno=-2 No such entry Somehow a reference byte has been corrupted and inserted into multiple locations in the tree and it's not repairable: i.e. neither a correct value can be inferred from other available information, nor do the tools have a good way to just trim out the item that contains bad key pointers - part of the problem with just cutting out the bad parts is it's not clear the problem is made even worse or how far the corruption extends. What's further troubling though is the idea that this corruption might have propagated to a separate volume via snapshot send receive. Either of the file systems might still be useful for a developer, it seems to me important to have some kind of check to make sure it's not possible for corruption to propagate in this manner. In the meantime, I think it's a good idea to do a memory test. There's some information in the archives about how to do this in a more reliable way than just memtest86 type tests, but if you can run even a memtest86 over a weekend it might confirm there's a memory problem. Unfortunately a pass doesn't necessarily mean there aren't rare transient problems. Chris Murphy
