mount(2) - SerenityOS man pages


mount - mount a filesystem


#include <unistd.h>

int mount(int source_fd, const char* target, const char* fs_type, int flags);


mount() mounts a filesystem stored at source_fd by overlaying its contents over target.

fs_type must be one of the following supported filesystems:

For Ext2FS, source_fd must refer to an open file descriptor to a file containing the filesystem image. This may be a device file or any other seekable file. For Plan9FS, source_fd must refer to a socket or a device connected to a 9P server. All the other filesystems ignore the source_fd - you can even pass an invalid file descriptor such as -1.

The following flags are supported:

These flags can be used as a security measure to limit the possible abuses of the newly mounted file system.

Bind mounts

If MS_BIND is specified in flags, fs_type is ignored and a bind mount is performed instead. In this case, the file or directory specified by source_fd is overlaid over target — the target appears to be replaced by a copy of the source. This can be used as an alternative to symlinks or hardlinks.

Each bind mount has its own set of flags, independent of the others or the original file system. It is possible to bind-mount a file or directory over itself, which may be useful for changing mount flags for a part of a filesystem.


Note that remounting a file system will only affect future operations with the file system, not any already opened files. For example, if you open a directory on a filesystem that's mounted with MS_NODEV, then remount the filesystem to allow opening devices, attempts to open a devices relative to the directory file descriptor (such as by using openat()) will still fail.

In particular, current working directory and root directory of any already running processes behave the same way, and don't automatically "pick up" changes in mount flags of the underlying file system. To "refresh" the working directory to use the new mount flags after remounting a filesystem, a process can call chdir() with the path to the same directory.


All of the usual path resolution errors may also occur.

See also