HowTo: Create a Hard Links in Linux / UNIX

last updated in Categories , , , , , , , , ,

Both Linux / UNIX allows the data of a file to have more than one name in separate places in the same file system. Such a file with more than one name for the same data is called a hard-linked file. How do I create a hard link under Linux / UNIX / Apple Mac OS X / BSD operating systems?

A hard link to a file is indistinguishable from the original directory entry; any changes to a file are effectively independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file systems.

ln command Example To Make a Hard Link

The ln command make links between files. By default, ln makes hard links.

ln Command Syntax

The syntax is as follows for Unix / Linux hard link command:

ln {source} {link}


  • source is an existing file.
  • link is the file to create (a hard link).

To create hard link for foo file, enter:
echo 'This is a test' > foo
ln foo bar
ls -li bar foo

Sample outputs:

4063240 -rw-r--r-- 2 root root 15 Oct  1 15:30 bar
4063240 -rw-r--r-- 2 root root 15 Oct  1 15:30 foo

Hard Links Limitations

There are some issues with hard links that can sometimes make them unsuitable. First of all, because the link is identical to the thing it points to, it becomes difficult to give a command such as “list all the contents of this directory recursively but ignore any links”. Most modern operating systems don’t allow hard links on directories to prevent endless recursion. Another drawback of hard links is that they have to be located within the same file system, and most large systems today consist of multiple file systems.

Posted by: Vivek Gite

The author is the creator of nixCraft and a seasoned sysadmin, DevOps engineer, and a trainer for the Linux operating system/Unix shell scripting. Get the latest tutorials on SysAdmin, Linux/Unix and open source topics via RSS/XML feed or weekly email newsletter.

11 comment

  1. Another drawback of hard links is that they have to be located within the same file system, and most large systems today consist of multiple file systems.

    Does mean, for example, you cannot make a hard link between and ext3 and ext4 file system, or does it mean you cannot link between file systems on two separate volumes?

    I know this is two years old, but maybe some is watching? I have seen the above quote in a number of sources, but this one is the only one where there’s a chance to ask.

    1. We are talking about two devices. For example /dev/sdc1 mounted on /disk1 and /dev/sdd1 mounted on /disk2. You can not create a hard link between /disk1 and /disk2. You will get an error as follows if you try:

      ln: creating hard link `hard' => `/disk2/somefile': Invalid cross-device link

      Also, you can not format /dev/sdd1 as ext3 or ext4 at the same time or mount same device as ext3 or ext4 as same time as you need to format the file system. In short, hard link is not allowed between cross devices (it does not matter if devices are formatted as ext3 or ext4).

  2. Thanks for the clarification and thanks for still watching this thread. Hope your reply will be useful to others who come across your excellent blog, by searching.

    Now, because of what you said, I may instead try to get a similar result using ‘mount –bind’.

    I’m trying to get the ‘/doc’ from ‘usr/share/doc’ off of a small SSD and onto a separate ‘/doc’ on a MMC in the memory slot of the same netbook. As well, I think the above command should also be insensitive to the SSD being ext4 and the MMC being formatted in ext3.

    1. Roland,

      If I understood the question properly you could:
      $ cd dir-the-file-is-in
      $ ls -li filename*
      $ cd /
      $ find . -inum “23432432” -exec ls -li {} \;

      Replace the inod number with what you received from the first command. The exec part is optional. All depends on how much info you want upon finding the files.

      Hope that helps.


  3. Thank you! This was exactly what I needed on my Mac! It is perfect to link files between two Git repositories :)

    Have a question? Post it on our forum!