1.\" Copyright (c) 1980, 1989, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 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. 19.\" 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 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)mount.8 8.8 (Berkeley) 6/16/94 33.\" $FreeBSD: src/sbin/mount/mount.8,v 1.31.2.12 2003/02/23 21:17:42 trhodes Exp $ 34.\" $DragonFly: src/sbin/mount/mount.8,v 1.4 2006/02/17 19:33:32 swildner Exp $ 35.\" 36.Dd June 16, 1994 37.Dt MOUNT 8 38.Os 39.Sh NAME 40.Nm mount 41.Nd mount file systems 42.Sh SYNOPSIS 43.Nm 44.Op Fl adfpruvw 45.Op Fl o Ar options 46.Op Fl t Ar ufs | external_type 47.Nm 48.Op Fl dfpruvw 49.Ar special | node 50.Nm 51.Op Fl dfpruvw 52.Op Fl o Ar options 53.Op Fl t Ar ufs | external_type 54.Ar special node 55.Sh DESCRIPTION 56The 57.Nm 58utility calls the 59.Xr mount 2 60system call to prepare and graft a 61.Ar "special device" 62or the remote node (rhost:path) on to the file system tree at the point 63.Ar node . 64If either 65.Ar special 66or 67.Ar node 68are not provided, the appropriate information is taken from the 69.Xr fstab 5 70file. 71.Pp 72The system maintains a list of currently mounted file systems. 73If no arguments are given to 74.Nm , 75this list is printed. 76.Pp 77The options are as follows: 78.Bl -tag -width indent 79.It Fl a 80All the filesystems described in 81.Xr fstab 5 82are mounted. 83Exceptions are those marked as 84.Dq noauto , 85excluded by the 86.Fl t 87flag (see below), or if they are already mounted (except the 88root filesystem which is always remounted to preserve 89traditional single user mode behavior). 90.It Fl d 91Causes everything to be done except for the actual system call. 92This option is useful in conjunction with the 93.Fl v 94flag to 95determine what the 96.Nm 97command is trying to do. 98.It Fl f 99Forces the revocation of write access when trying to downgrade 100a filesystem mount status from read-write to read-only. 101Also 102forces the R/W mount of an unclean filesystem (dangerous; use with 103caution). 104.It Fl o 105Options are specified with a 106.Fl o 107flag followed by a comma separated string of options. 108In case of conflicting options being specified, the rightmost option 109takes effect. 110The following options are available: 111.Bl -tag -width indent 112.It Cm async 113All 114.Tn I/O 115to the file system should be done asynchronously. 116This is a 117.Em dangerous 118flag to set, 119and should not be used unless you are prepared to recreate the file 120system should your system crash. 121.It Cm current 122When used with the 123.Fl u 124flag, this is the same as specifying the options currently in effect for 125the mounted filesystem. 126.It Cm force 127The same as 128.Fl f ; 129forces the revocation of write access when trying to downgrade 130a filesystem mount status from read-write to read-only. 131Also 132forces the R/W mount of an unclean filesystem (dangerous; use with caution). 133.It Cm fstab 134When used with the 135.Fl u 136flag, this is the same as specifying all the options listed in the 137.Xr fstab 5 138file for the filesystem. 139.It Cm noasync 140Metadata I/O should be done synchronously, while data I/O should be done 141asynchronously. 142This is the default. 143.It Cm noatime 144Do not update the file access time when reading from a file. 145This option 146is useful on filesystems where there are large numbers of files and 147performance is more critical than updating the file access time (which is 148rarely ever important). 149This option is currently only supported on local filesystems. 150.It Cm noauto 151This filesystem should be skipped when 152.Nm 153is run with the 154.Fl a 155flag. 156.It Cm noclusterr 157Disable read clustering. 158.It Cm noclusterw 159Disable write clustering. 160.It Cm nodev 161Do not interpret character or block special devices on the file system. 162This option is useful for a server that has file systems containing 163special devices for architectures other than its own. 164This option is set automatically when the user does not have super-user 165privileges. 166.It Cm noexec 167Do not allow execution of any binaries on the mounted file system. 168This option is useful for a server that has file systems containing 169binaries for architectures other than its own. 170.It Cm nosuid 171Do not allow set-user-identifier or set-group-identifier bits to take effect. 172Note: this option is worthless if a public available suid or sgid 173wrapper like 174.Xr suidperl 1 175is installed on your system. 176It is set automatically when the user does not have super-user privileges. 177.It Cm nosymfollow 178Do not follow symlinks 179on the mounted file system. 180.It Cm rdonly 181The same as 182.Fl r ; 183mount the file system read-only (even the super-user may not write it). 184.It Cm sync 185All 186.Tn I/O 187to the file system should be done synchronously. 188.It Cm suiddir 189A directory on the mounted filesystem will respond to the SUID bit 190being set, by setting the owner of any new files to be the same 191as the owner of the directory. 192New directories will inherit the bit from their parents. 193Execute bits are removed from 194the file, and it will not be given to root. 195.Pp 196This feature is designed for use on fileservers serving PC users via 197ftp, SAMBA, or netatalk. 198It provides security holes for shell users and as 199such should not be used on shell machines, especially on home directories. 200This option requires the SUIDDIR 201option in the kernel to work. 202Only UFS filesystems support this option. 203See 204.Xr chmod 2 205for more information. 206.It Cm update 207The same as 208.Fl u ; 209indicate that the status of an already mounted file system should be changed. 210.It Cm union 211Causes the namespace at the mount point to appear as the union 212of the mounted filesystem root and the existing directory. 213Lookups will be done in the mounted filesystem first. 214If those operations fail due to a non-existent file the underlying 215directory is then accessed. 216All creates are done in the mounted filesystem. 217.El 218.Pp 219Any additional options specific to a filesystem type that is not 220one of the internally known types (see the 221.Fl t 222option) may be passed as a comma separated list; these options are 223distinguished by a leading 224.Dq \&- 225(dash). 226Options that take a value are specified using the syntax -option=value. 227For example, the 228.Nm 229command: 230.Bd -literal -offset indent 231mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp 232.Ed 233.Pp 234causes 235.Nm 236to execute the equivalent of: 237.Bd -literal -offset indent 238/sbin/mount_mfs -o nosuid -N -s 4000 /dev/dk0b /tmp 239.Ed 240.Pp 241Additional options specific to filesystem types 242which are not internally known 243(see the description of the 244.Fl t 245option below) 246may be described in the manual pages for the associated 247.Pa /sbin/mount_ Ns Sy XXX 248utilities. 249.It Fl p 250Print mount information in 251.Xr fstab 5 252format. 253Implies also the 254.Fl v 255option. 256.It Fl r 257The file system is to be mounted read-only. 258Mount the file system read-only (even the super-user may not write it). 259The same as the 260.Cm rdonly 261argument to the 262.Fl o 263option. 264.It Fl t Ar ufs | external_type 265The argument following the 266.Fl t 267is used to indicate the file system type. 268The type 269.Ar ufs 270is the default. 271The 272.Fl t 273option can be used 274to indicate that the actions should only be taken on 275filesystems of the specified type. 276More than one type may be specified in a comma separated list. 277The list of filesystem types can be prefixed with 278.Dq no 279to specify the filesystem types for which action should 280.Em not 281be taken. 282For example, the 283.Nm 284command: 285.Bd -literal -offset indent 286mount -a -t nonfs,mfs 287.Ed 288.Pp 289mounts all filesystems except those of type 290.Tn NFS 291and 292.Tn MFS . 293.Pp 294If the type is not one of the internally known types, 295.Nm 296will attempt to execute a program in 297.Pa /sbin/mount_ Ns Sy XXX 298where 299.Sy XXX 300is replaced by the type name. 301For example, nfs filesystems are mounted by the program 302.Pa /sbin/mount_nfs . 303.Pp 304Most filesystems will be dynamically loaded by their 305.Nm 306programs 307if not already present in the kernel, using the 308.Xr vfsload 3 309subroutine. 310Because this mechanism requires writable temporary space, 311the filesystem type containing 312.Pa /tmp 313must be compiled into the kernel, and the filesystems containing 314.Pa /tmp 315and 316.Pa /usr/bin/ld 317must be listed in 318.Pa /etc/fstab 319before any filesystems which might be dynamically loaded. 320.It Fl u 321The 322.Fl u 323flag indicates that the status of an already mounted file 324system should be changed. 325Any of the options discussed above (the 326.Fl o 327option) 328may be changed; 329also a file system can be changed from read-only to read-write 330or vice versa. 331An attempt to change from read-write to read-only will fail if any 332files on the filesystem are currently open for writing unless the 333.Fl f 334flag is also specified. 335The set of options is determined by applying the options specified 336in the argument to 337.Fl o 338and finally applying the 339.Fl r 340or 341.Fl w 342option. 343.It Fl v 344Verbose mode. 345.It Fl w 346The file system object is to be read and write. 347.El 348.Sh FILES 349.Bl -tag -width /etc/fstab -compact 350.It Pa /etc/fstab 351file system table 352.El 353.Sh DIAGNOSTICS 354Various, most of them are self-explanatory. 355.Pp 356.Dl XXXXX filesystem is not available 357.Pp 358The kernel does not support the respective filesystem type. 359Note that 360support for a particular filesystem might be provided either on a static 361(kernel compile-time), or dynamic basis (loaded as a kernel module by 362.Xr kldload 8 ) . 363Normally, 364.Nm 365or its subprocesses attempt to dynamically load a filesystem module if 366it has not been configured statically, using 367.Xr vfsload 3 . 368In this case, the above error message can also mean that you did not 369have permission to load the module. 370.Sh SEE ALSO 371.Xr mount 2 , 372.Xr vfsload 3 , 373.Xr fstab 5 , 374.Xr kldload 8 , 375.Xr mount_cd9660 8 , 376.Xr mount_ext2fs 8 , 377.Xr mount_fdesc 8 , 378.Xr mount_linprocfs 8 , 379.Xr mount_mfs 8 , 380.Xr mount_msdos 8 , 381.Xr mount_nfs 8 , 382.Xr mount_ntfs 8 , 383.Xr mount_null 8 , 384.Xr mount_nwfs 8 , 385.Xr mount_portal 8 , 386.Xr mount_procfs 8 , 387.Xr mount_smbfs 8 , 388.Xr mount_std 8 , 389.Xr mount_umap 8 , 390.Xr mount_union 8 , 391.Xr sysctl 8 , 392.Xr umount 8 393.Sh CAVEATS 394After a successful 395.Nm , 396the permissions on the original mount point determine if 397.Pa ..\& 398is accessible from the mounted file system. 399The minimum permissions for 400the mount point for traversal across the mount point in both 401directions to be possible for all users is 0111 (execute for all). 402.Sh HISTORY 403A 404.Nm 405utility appeared in 406.At v1 . 407.Sh BUGS 408It is possible for a corrupted file system to cause a crash. 409