Thanks for the suggestion.
I would like to see file names printed by fsck, something like this:
$ fsck /dev/sdb1
Inode 310945 (/foobar/somefile.txt) has a extra size (33252) which is invalid
In this case, /foobar/somefile.txt
is the file name, as seen from the root of the filesystem on /dev/sdb1
, that is affected by the inode problem that fsck found.
That doesn't appear possible with fsck.
So the next best thing I'm trying to achieve is a method that would associate inode numbers with file names before fsck makes changes to the filesystem.
This way I can understand the files that will be affected by fsck (instead of inodes affected, which for me the end-user, is useless).