At first, I though we could create a comprehensive list of detectable problems of Sanitizer. Basically, making of human-readable list of the integrity check. But that’s quite a lot of effort.
What orphan message are you getting exactly? There are
OrphanMFile afaik. If my guess is right that you meant “files”, it should be
OrphanMFile. In that case, this is indeed “normal” (that’s why it’s just an
If you create a file or folder with a very long name, it’s getting shortened (see name shortening in security architecture). The folder
m (stands for metadata) currently only contains shortened file/folder names. If you rename/move/delete a file/folder with a long name, the corresponding metadata file won’t get deleted. That’s why some metadata files can get orphaned over time. If your vault is fully(!) synchronized, it’s safe to delete orphaned metadata files. You can actually use Sanitizer to do that by adding the
--solve OrphanMFile parameter.
I can’t find the discussion anymore but there was a time when it was necessary not to delete metadata files. If I’m not mistaken, due to some changes in the encryption scheme, we actually can safely delete metadata files now. Would have to discuss this with the others if that’s an improvement that we could make in a future version.