If you ever encounter an error when checking an APFS volume using First Aid in Disk Utility or fsck_apfs, you won’t be informed of the path and name of the item responsible, but given its inode number, in an entry like
warning: inode (id 402194151): Resource Fork xattr is missing for compressed file

As I explained at the end of August, while there are ways of converting an inode number to a path and name, they require a bit of juggling around with Terminal. To make this more readily accessible, this new version of my free utility Mints can now resolve an inode number to a name and path for you.

This new feature is accessed through the Inode item in the Data… command in Mints’ Window menu. That opens an Inode Resolver window to perform the conversion.

Inode numbers are used in a special low-level file system known as volfs, which works entirely in numbers. To give a volfs path you need two very large integers: the number for the volume, and that for the file or folder within that volume. While APFS errors give the second of those, they leave you to discover the first for yourself.

To do that, you’ll need to confirm which volume was being checked at the time of the error, which should be the same as the volume you ran First Aid or fsck_apfs on. Unfortunately this gets more complicated with snapshots, where they should have the same volume number as the original volume from which they were made (I think). All you need do then is drag and drop a file or folder from the same volume onto the Inode Resolver window, which will highlight as Mints works out the item’s volfs path, then displays it in the window.

Although it can sometimes be useful to get the full volfs path for a file or folder, you can already do that using Precize, or other tools. Click on the window’s Resolve button and it will give you further information about that file, including its regular path and name.

Provided that APFS or whatever has given you the inode number of the item on that volume, all you need do now is paste that into the Inode Number box at the top of the resolver window, and click Resolve again. Mints then looks up information for that inode number on the same volume, using GetFileInfo, and displays it below.

One drag and drop, a paste, and a click to discover what APFS is complaining about.

Mints version 1.15 is available from here: mints115
from Downloads above, from its Product Page, and through its auto-update mechanism.

I apologise that it has taken me so long to provide this useful feature in Mints.