Aha. find found the inode in lost+found/ . So, whatever it is, the data was already not where it was supposed to be. Suppose that means it’s not important, since I haven’t noticed it missing. Although, that’s not guaranteed. file cannot read the data, though: cannot open #8331004 (structure needs cleaning). Sounds like your suggestion is the best plan. I guess I could try to back up the whole FS, but I actually don’t think I have…oh, well, I think I do actually have something big enough to back it up. But, I don’t think I will. We’ll just see what fsck says.
Dang. That didn’t help. fsck didn’t find anything wrong. I tried -f-D and -E fragcheck, too, and they also didn’t fix anything. However, when I tried -E discard, it did report that that FS had errors, but I think that it says that whenever this option is used, because all previous runs didn’t say that. But, discard did generate the same error about that particular inode and “structure needs cleaning”. I forgot to make notes while I was in boot singe mode, so I might not be remembering everything correct.
The upshot is that I still have that error about “structure needs cleaning” when I try to read, rm, or find that file.