Why can't I mount the same filesystem at multiple points, and why can't a mount-point inode reference count be > 1?

Solution 1:

The HP (HP-UX) man page for mount(2) says:

If mount() fails, errno is set to one of the following values.

• [EACCES] A component of the path prefix denies search permission.
• [EBUSY] path is currently mounted on, is someone's current working directory, or is otherwise busy.
• [EBUSY] The file system associated with fs is currently mounted.

You get the first EBUSY when your question (1) applies because:

• if the directory is already a mount point, you lose access to the previously mounted directory, which makes the prior mount irrelevant.
• if the directory (say /some/where) is some process's current directory, you have a process with a different view of the contents of /some/where; newcomers see what's on the mounted file system, but the old processes see what was in the mounted-upon directory.

You get the second EBUSY to answer your question (2) when the file system is already mounted - in other words, you can't mount it twice. This is a good thing - there would be a dreadful danger of confusion if two separate mount points both went around assuming they had exclusive access to the superblock etc when it was in fact shared. It would also be confusing if creating a file /some/where/newfile also simultaneously created /opt/other/newfile because the same device was mounted on both /some/where and /opt/other.

I haven't checked the AIX, Solaris, Linux, MacOS X, BSD man pages for mount(2), but I expect the behaviour to be the same.

Solution 2:

This isn't a direct answer, but you can get behavior similar to mounting in two places by using mount --bind

Solution 3:

Basically the possibility of mounting one filesystem at several places breaks the concept of a tree hierarchical filesystem, converting it in a directed acyclic graph (even you can try to mount a mounted filesystem into a subdirectory of itshelf, breaking more to a possible cyclic, nondirected general graph). Basically, the problem is that when you try to pass up to the parent directory using the .. entry in the mounted root directory, you have to select which of the now several parent directories to follow to get to the parent.

In linux, there's a --bind option to mount that allows you to mount a directory (not necessary for it to be a root directory on a filesystem) at some other place (not a mounted filesystem, but a plain directory) so you can mount things like the /proc or /sys filesystems on chroot(2)ed processes and let them access to this framework.

This kind of mount is different in the same sense as the diference between soft and hard links to files. It's treated differently by the kernel and it only allows a true mount point per root filesystem. The reason is basically the same as you cannot create loops with hard links and you can with soft. You cannot mount again a mounted filesystem, and you can mount --bind several times the same directory.