The post explains some of the common error messages from command xfs_repair and the repairs that it performs.
disconnected inode 242002, moving to lost+found
xfs_repair found an inode that is in use but is not connected to the filesystem. The inode is moved to the filesystem’s lost+found directory. Its name is its inode number (in this example, 242002). If the disconnected inode is a directory, the directory’s subtree is preserved–all of its child inodes are automatically moved with it. So, the entire directory subtree moves to lost+found.
imap claims in-use inode 2444941 is free, correcting imap
The inode allocation map in the filesystem behaves as if inode 2444941(in this example) is free, but the inode itself looks like it is still in use.xfs_repair corrects the inode map to say that the inode is in use.
entry references free inode 2444940 in shortform directory 2444922 junking entry “test” in directory inode 2444922
A directory entry points to an inode (in this example, 2444940) that xfs_repair has determined is actually free.xfs_repair junks the directory entry. The term shortform means a small directory. In larger directories, the entry deletion is usually a two-pass process. In this case, the second part of the message reads something like marking bad entry, marking the entry to be deleted, or will clear entry.
resetting inode 241996 nlinks from 5 to 3
xfs_repair detected a mismatch between the number of directory entries pointing to the inode (in this example, 241996) and the number of links recorded in the inode. It corrected the number (from 5 to 3 in this case).
cleared inode 2444926
There was something wrong with the inode that was not correctable, so xfs_repair turned it into a zero-length free inode. This usually happens because the inode claims block that is used by something else or the inode itself is badly corrupted. Typically, the cleared inode message is preceded by one or more messages indicating why the inode must be cleared.