Skip to main content
In this article, we’ll explore how Linux manages hard links and why they are beneficial for efficient file management. Understanding hard links requires a basic knowledge of file systems and inodes.

​
File System Basics

Imagine a Linux system used by two distinct users, Aaron and Jane. Each user logs in with their own credentials, which provide personalized desktops, settings, and file directories. Suppose Aaron takes a picture of the family dog and saves it as: /home/aaron/pictures/family_dog.jpg To simulate the file creation, we use the following command, which writes a description (acting as the file’s content) into the file:
When you inspect the file with the stat command, it shows details that include the inode number:
In Linux, every file is represented by an inode—a data structure that stores metadata (like permissions, modification times, and data block locations). While the inode number is the technical reference, we use the file name (in this case, family_dog.jpg) to map to that inode. Notice the output indicates “Links: 1”, meaning there is a single hard link (the original file name) associated with the inode. Hard links allow you to reference the same data from different locations without duplicating file content. This is especially useful if you want to share data without unnecessarily consuming additional disk space. Consider Jane, who has her own pictures directory at /home/jane/pictures. Instead of copying family_dog.jpg from Aaron’s directory, which duplicates the file data, you can create a hard link. This avoids the overhead of duplicating thousands of high-resolution images. While the typical copy command might be:
you can create a hard link using the following syntax:
After creating the hard link, both file paths reference the same inode. Running the stat command now will show the file has two hard links:
If one user deletes their reference (hard link) to the file, the data remains accessible through the other link. The file data is only removed when the last hard link is deleted.
For example, if Aaron removes his file:
Jane still has access via her hard link. However, if Jane then deletes the file as well:
the filesystem marks the data blocks as free, and from the user’s perspective, the file is gone. Since hard links share the same inode, any permission changes on one link are reflected on all links. To ensure both Aaron and Jane have correct access to the file, you might add them to the same group (for example, “family”) and adjust the file’s permissions accordingly:
These permission changes apply to all hard links referencing the inode, ensuring consistent access. There are a few limitations to be aware of when working with hard links:
  1. Hard links can only be created for files, not directories.
  2. Hard links must reside on the same file system; you cannot create a hard link from one file system to another.
The image is a diagram explaining the limitations of hard links, showing that hard links can only be created for files, not folders, and must be on the same filesystem.
Remember, attempting to create a hard link across different file systems or for directories will result in an error.

​
Summary

Hard links allow multiple directory entries to reference the same file data without duplicating storage capacity. This method provides an efficient way to share files between users while ensuring that the data remains accessible until all links are removed. For further reading on Linux file systems and inode management, consider visiting Linux File System Hierarchy.

Watch Video