It makes a big difference whether an app, file or folder is in the System or Data volume, or maybe somewhere else. Here’s how to tell accurately, rather than according to one of the Finder’s illusions.
inode
First Aid in Disk Utility, or fsck_apfs in Terminal, have given warnings or errors with id numbers. How do you work out which file or folder that refers to?
How APFS is the first Mac native file system to have true inodes and inode numbers. What they are, and how you can use them in volume groups and different types of file link.
A full toolset for working with extended attributes, everything you might want to know about files, and a text-only Rich Text editor, all ready for Tahoe.
B+trees, directory records, directory and file names and Unicode normalisation, and whatever happened to the promise of fast directory sizing?
We’re almost unaware of clone files, and how they’ve changed macOS. But look at most documents that have been saved more than once, and you’ll see they’ve now be cloned.
Understanding how APFS works: inodes, attributes, file extents, extended attributes, and how they change with editing and cloning.
How inode numbers can give important insights into the structure of the conjoined System and Data volumes, and help you navigate them.
Adds a new feature that will resolve an inode number, such as that given in an APFS error or warning, to give you the item name and path.
When you run First Aid, its reports an error with an inode. Here’s how to identify the item responsible by converting that inode number to a file path.
