1 .\" Copyright (c) 1980, 1989, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)mount.2 8.3 (Berkeley) 5/24/95
33 .\" $FreeBSD: src/lib/libc/sys/mount.2,v 1.20.2.8 2003/01/17 22:02:42 joerg Exp $
41 .Nd mount or dismount a filesystem
48 .Fn mount "const char *type" "const char *dir" "int flags" "void *data"
50 .Fn unmount "const char *dir" "int flags"
55 a filesystem object onto the system file tree
60 describes the filesystem object to be mounted.
63 tells the kernel how to interpret
68 The contents of the filesystem
69 become available through the new mount point
74 of a successful mount are swept under the carpet so to speak, and
75 are unavailable until the filesystem is unmounted.
77 By default only the super-user may call the
80 This restriction can be removed by setting the sysctl
87 suppress default semantics which affect filesystem access.
88 .Bl -tag -width MNT_SYNCHRONOUS
90 The filesystem should be treated as read-only;
91 Even the super-user may not write on it.
92 Specifying MNT_UPDATE without this option will upgrade
93 a read-only filesystem to read/write.
95 Do not allow files to be executed from the filesystem.
97 Do not honor setuid or setgid bits on files when executing them.
98 This flag is set automatically when the caller is not the super-user.
100 Disable update of file access times.
102 Do not interpret special files on the filesystem.
103 This flag is set automatically when the caller is not the super-user.
105 Directories with the SUID bit set chown new files to their own owner.
106 .It Dv MNT_SYNCHRONOUS
107 All I/O to the filesystem should be done synchronously.
109 All I/O to the filesystem should be done asynchronously.
111 Force a read-write mount even if the filesystem appears to be unclean.
113 .It Dv MNT_NOCLUSTERR
114 Disable read clustering.
115 .It Dv MNT_NOCLUSTERW
116 Disable write clustering.
121 indicates that the mount command is being applied
122 to an already mounted filesystem.
123 This allows the mount flags to be changed without requiring
124 that the filesystem be unmounted and remounted.
125 Some filesystems may not allow all flags to be changed.
127 many filesystems will not allow a change from read-write to read-only.
131 causes the vfs subsystem to update its data structures pertaining to
132 the specified already mounted filesystem.
136 argument names the filesystem.
137 The types of filesystems known to the system can be obtained with
141 is a pointer to a structure that contains the type
142 specific arguments to mount.
143 The format for these argument structures is described in the
144 manual page for each filesystem.
145 By convention filesystem manual pages are named
146 by prefixing ``mount_'' to the name of the filesystem as returned by
150 filesystem is described by the
156 function call disassociates the filesystem from the specified
164 to specify that the filesystem should be forcibly unmounted or made read-only
165 (if MNT_UPDATE and MNT_RDONLY are also specified)
166 even if files are still active.
167 Active special devices continue to work,
168 but any further accesses to any other active files result in errors
169 even if the filesystem is later remounted.
173 option requires the SUIDDIR option to have been compiled into the kernel
179 pages for more information.
185 function will fail when one of the following occurs:
188 The caller is neither the super-user nor the owner of
190 .It Bq Er ENAMETOOLONG
191 A component of a pathname exceeded 255 characters,
192 or the entire length of a path name exceeded 1023 characters.
194 Too many symbolic links were encountered in translating a pathname.
207 Another process currently holds a reference to
211 points outside the process's allocated address space.
214 The following errors can occur for a
219 A component of ufs_args
224 is not a block device.
226 The major device number of
228 is out of range (this indicates no device driver exists
229 for the associated hardware).
234 No space remains in the mount table.
236 The super block for the filesystem had a bad magic
237 number or an out of range block size.
239 Not enough memory was available to read the cylinder
240 group information for the filesystem.
242 An I/O error occurred while reading the super block or
243 cylinder group information.
246 points outside the process's allocated address space.
249 The following errors can occur for a
255 timed out trying to contact the server.
257 Some part of the information described by nfs_args
258 points outside the process's allocated address space.
261 The following errors can occur for a
266 No space remains in the mount table.
268 The super block for the filesystem had a bad magic
269 number or an out of range block size.
271 Not enough memory was available to read the cylinder
272 group information for the filesystem.
274 A paging error occurred while reading the super block or
275 cylinder group information.
278 points outside the process's allocated address space.
283 function may fail with one of the following errors:
286 The caller is neither the super-user nor the user who issued the corresponding
290 A component of the path is not a directory.
291 .It Bq Er ENAMETOOLONG
292 A component of a pathname exceeded 255 characters,
293 or an entire path name exceeded 1023 characters.
295 Too many symbolic links were encountered in translating the pathname.
297 The requested directory is not in the mount table.
299 A process is holding a reference to a file located
302 An I/O error occurred while writing cached filesystem information.
305 points outside the process's allocated address space.
312 mount can also fail if the maximum number of filesystems are currently
321 Some of the error codes need translation to more obvious messages.
326 function calls appeared in