1 .\" Hey Emacs! This file is -*- nroff -*- source.
3 .\" Copyright (C) 1993 Rickard E. Faith <faith@cs.unc.edu>
4 .\" and Copyright (C) 1994 Andries E. Brouwer <aeb@cwi.nl>
5 .\" and Copyright (C) 2002, 2005 Michael Kerrisk <mtk.manpages@gmail.com>
7 .\" Permission is granted to make and distribute verbatim copies of this
8 .\" manual provided the copyright notice and this permission notice are
9 .\" preserved on all copies.
11 .\" Permission is granted to copy and distribute modified versions of this
12 .\" manual under the conditions for verbatim copying, provided that the
13 .\" entire resulting derived work is distributed under the terms of a
14 .\" permission notice identical to this one.
16 .\" Since the Linux kernel and libraries are constantly changing, this
17 .\" manual page may be incorrect or out-of-date. The author(s) assume no
18 .\" responsibility for errors or omissions, or for damages resulting from
19 .\" the use of the information contained herein. The author(s) may not
20 .\" have taken the same level of care in the production of this manual,
21 .\" which is licensed free of charge, as they might when working
24 .\" Formatted or processed versions of this manual, if unaccompanied by
25 .\" the source, must acknowledge the copyright and authors of this work.
27 .\" Modified 1996-11-04 by Eric S. Raymond <esr@thyrsus.com>
28 .\" Modified 2001-10-13 by Michael Kerrisk <mtk.manpages@gmail.com>
29 .\" Added note on historical behavior of MS_NOSUID
30 .\" Modified 2002-05-16 by Michael Kerrisk <mtk.manpages@gmail.com>
31 .\" Extensive changes and additions
32 .\" Modified 2002-05-27 by aeb
33 .\" Modified 2002-06-11 by Michael Kerrisk <mtk.manpages@gmail.com>
34 .\" Enhanced descriptions of MS_MOVE, MS_BIND, and MS_REMOUNT
35 .\" Modified 2004-06-17 by Michael Kerrisk <mtk.manpages@gmail.com>
36 .\" 2005-05-18, mtk, Added MNT_EXPIRE, plus a few other tidy-ups.
38 .TH MOUNT 2 2008-10-06 "Linux" "Linux Programmer's Manual"
40 mount \- mount file system
43 .B "#include <sys/mount.h>"
45 .BI "int mount(const char *" source ", const char *" target ,
46 .BI " const char *" filesystemtype ", unsigned long " mountflags ,
47 .BI " const void *" data );
51 attaches the file system specified by
53 (which is often a device name, but can also be a directory name
54 or a dummy) to the directory specified by
57 Appropriate privilege (Linux: the
59 capability) is required to mount file systems.
61 Since Linux 2.4 a single file system can be visible at
62 multiple mount points, and multiple mounts can be stacked
63 on the same mount point.
64 .\" Multiple mounts on same mount point: since 2.3.99pre7.
68 argument supported by the kernel are listed in
70 (like "minix", "ext2", "ext3", "jfs", "xfs", "reiserfs",
71 "msdos", "proc", "nfs", "iso9660" etc.).
72 Further types may become available when the appropriate modules
77 argument may have the magic number 0xC0ED (\fBMS_MGC_VAL\fP)
78 in the top 16 bits (this was required in kernel versions prior to 2.4, but
79 is no longer required and ignored if specified),
80 and various mount flags (as defined in \fI<linux/fs.h>\fP for libc4 and libc5
81 and in \fI<sys/mount.h>\fP for glibc2) in the low order 16 bits:
82 .\" FIXME 2.6.15 added flags for "shared sub-tree" functionality:
83 .\" MS_UNBINDABLE, MS_PRIVATE, MS_SHARED, MS_SLAVE
84 .\" These need to be documented on this page.
86 .\" Documentation/filesystems/sharedsubtree.txt
88 .\" http://lwn.net/Articles/159077/
90 .\" http://myweb.sudhaa.com:2022/~ram/sharedsubtree/paper/sharedsubtree.1.pdf
91 .\" Shared-Subtree Concept, Implementation, and Applications in Linux
92 .\" Al Viro viro@ftp.linux.org.uk
93 .\" Ram Pai linuxram@us.ibm.com
95 .\" http://foss.in/2005/slides/sharedsubtree1.pdf
96 .\" Shared Subtree Concept and Implementation in the Linux Kernel
100 .BR MS_BIND " (Linux 2.4 onwards)"
101 .\" since 2.4.0-test9
102 Perform a bind mount, making a file or a directory subtree visible at
103 another point within a file system.
104 Bind mounts may cross file system boundaries and span
111 arguments are ignored.
112 Up until Linux 2.6.26,
115 .\" with the exception of the "hidden" MS_REC mountflags bit
116 (the bind mount has the same mount options as
117 the underlying mount point).
118 Since Linux 2.6.26, the
120 flag is honored when making a bind mount.
122 .BR MS_DIRSYNC " (since Linux 2.5.19)"
123 Make directory changes on this file system synchronous.
124 (This property can be obtained for individual directories
129 Permit mandatory locking on files in this file system.
130 (Mandatory locking must still be enabled on a per-file basis,
133 .\" FIXME Say more about MS_MOVE
138 specifies an existing mount point and
140 specifies the new location.
141 The move is atomic: at no point is the subtree unmounted.
143 .IR filesystemtype ", " mountflags ", and " data
144 arguments are ignored.
147 Do not update access times for (all types of) files on this file system.
150 Do not allow access to devices (special files) on this file system.
153 Do not update access times for directories on this file system.
154 This flag provides a subset of the functionality provided by
162 Do not allow programs to be executed from this file system.
163 .\" (Possibly useful for a file system that contains non-Linux executables.
164 .\" Often used as a security feature, e.g., to make sure that restricted
165 .\" users cannot execute files uploaded using ftp or so.)
168 Do not honor set-user-ID and set-group-ID bits when executing
169 programs from this file system.
170 .\" (This is a security feature to prevent users executing set-user-ID and
171 .\" set-group-ID programs from removable disk devices.)
174 Mount file system read-only.
176 .\" FIXME Document MS_REC, available since 2.4.11.
177 .\" This flag has meaning in conjunction with MS_BIND and
178 .\" also with the shared sub-tree flags.
180 .BR MS_RELATIME " (Since Linux 2.6.20)"
181 When a file on this file system is accessed,
182 only update the file's last access time (atime) if the current value
183 of atime is less than or equal to the file's last modification time (mtime)
184 or last status change time (ctime).
185 This option is useful for programs, such as
187 that need to know when a file has been read since it was last modified.
190 Remount an existing mount.
191 This allows you to change the
195 of an existing mount without having to unmount and remount the file system.
199 should be the same values specified in the initial
211 before kernel 2.6.16, the following could also be changed:
215 and, additionally, before kernel 2.4.10, the following could also be changed:
220 .BR MS_SILENT " (since Linux 2.6.17)"
221 Suppress the display of certain
223 warning messages in the kernel log.
224 This flag supersedes the misnamed and obsolete
226 flag (available since Linux 2.4.12), which has the same meaning.
229 Make writes on this file system synchronous (as though
234 was specified for all file opens to this file system).
236 From Linux 2.4 onwards, the
237 .BR MS_NODEV ", " MS_NOEXEC ", and " MS_NOSUID
238 flags are settable on a per-mount-point basis.
239 From kernel 2.6.16 onwards,
243 are also settable on a per-mount-point basis.
246 flag is also settable on a per-mount-point basis.
250 argument is interpreted by the different file systems.
251 Typically it is a string of comma-separated options
252 understood by this file system.
255 for details of the options available for each filesystem type.
257 On success, zero is returned.
258 On error, \-1 is returned, and
260 is set appropriately.
262 The error values given below result from filesystem type independent
264 Each filesystem type may have its own special errors and its
265 own special behavior.
266 See the kernel source code for details.
269 A component of a path was not searchable.
271 .BR path_resolution (7).)
272 Or, mounting a read-only filesystem was attempted without giving the
277 is located on a filesystem mounted with the
280 .\" mtk: Probably: write permission is required for MS_BIND, with
281 .\" the error EPERM if not present; CAP_DAC_OVERRIDE is required.
286 Or, it cannot be remounted read-only,
287 because it still holds files open for writing.
288 Or, it cannot be mounted on
292 is still busy (it is the working directory of some task,
293 the mount point of another device, has open files, etc.).
296 One of the pointer arguments points outside the user address space.
300 had an invalid superblock.
305 was not already mounted on
311 was not a mount point, or was \(aq/\(aq.
314 Too many links encountered during pathname resolution.
315 Or, a move was attempted, while
321 (In case no block device is required:)
322 Table of dummy devices is full.
325 A pathname was longer than
330 not configured in the kernel.
333 A pathname was empty or had a nonexistent component.
336 The kernel could not allocate a free page to copy filenames or data into.
340 is not a block device (and a device was required).
349 The major number of the block device
354 The caller does not have the required privileges.
356 This function is Linux-specific and should not be used in
357 programs intended to be portable.
366 was added to \fI<mman.h>\fP.
368 Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program
369 on a filesystem mounted with
373 Since Linux 2.4 the set-user-ID and set-group-ID bits are
374 just silently ignored in this case.
375 .\" The change is in patch-2.4.0-prerelease.
378 .BR path_resolution (7),