Locate files and hardlinks by inode number quickly on the command line. 14.02.2026 | reading time: 2 min Locate files by their inode number to track hardlinks or recover orphaned data; concise examples show the exact commands to run and why they work. Hunt a missing hardlink Create a small test and reproduce the search using find and stat.\n```\nprintf 'Hello\n' > fileA\nln fileA fileB\nls -li fileA fileB\ninode=$(stat -c %i fileA)\necho $inode\nfind . -inum $inode -print\n```\nSample output (example values):\n```\n-rw-r--r-- 2 user user 6 Feb 14 12:00 fileA\n-rw-r--r-- 2 user user 6 Feb 14 12:00 fileB\n1234567\n./fileA\n./fileB\n``` Hands-on techniques Read an inode with `ls -i` or `stat -c %i`, then feed that number to `find . -inum N` to list every directory entry that points to the same inode; to discover multiple names use `find . -links +1` and inspect link counts with `ls -l`. When files behave oddly Remember that network and pseudo filesystems can expose different inode semantics, deleted-but-open files still occupy inodes until processes close them so use `lsof` to find holders, and tools like `debugfs` can inspect on-disk inode metadata on ext filesystems. Final step Try these commands on a disposable test directory, adapt them to a real recovery task, and keep exploring filesystem internals to become faster and more confident; consider formal certification to consolidate skills. Join Bits & Bytes Academy First class LINUX exam preparation. filesystem utilities troubleshooting storage scripting
