1 .\" Copyright (c) 1980, 1989, 1991, 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 .\" @(#)fstab.5 8.1 (Berkeley) 6/5/93
33 .\" $FreeBSD: src/share/man/man5/fstab.5,v 1.11.2.8 2003/02/10 12:21:08 des Exp $
40 .Nd static information about the filesystems
46 contains descriptive information about the various file
49 is only read by programs, and not written;
50 it is the duty of the system administrator to properly create
51 and maintain this file.
52 Each filesystem is described on a separate line;
53 fields on each line are separated by tabs or spaces.
54 The order of records in
61 sequentially iterate through
67 describes the block special device or
68 remote filesystem to be mounted.
69 For filesystems of type
71 the special file name is the block special file name,
72 and not the character special file name.
73 If a program needs the character special file name,
74 the program must create it by appending a ``r'' after the
75 last ``/'' in the special file name.
79 describes the mount point for the filesystem.
80 For swap partitions, this field should be specified as ``none''.
84 describes the type of the filesystem.
85 The system can support various filesystem types.
86 Only the root, /usr, and /tmp filesystems need be statically
87 compiled into the kernel;
88 everything else will be automatically loaded at mount
89 time. (Exception: the UFS family - FFS, MFS, and LFS cannot
90 currently be demand-loaded.) Some people still prefer to statically
91 compile other filesystems as well.
92 .Bl -tag -width indent -offset indent
102 a Sun Microsystems compatible ``Network File System''
104 a disk partition to be used for swapping
106 a DOS compatible filesystem
108 a CD-ROM filesystem (as per ISO 9660)
109 .\" maybe also say Rock Ridge extensions are handled ?
111 a file system for accessing process data
116 describes the mount options associated with the filesystem.
117 It is formatted as a comma separated list of options.
118 It contains at least the type of mount (see
120 below) plus any additional options
121 appropriate to the filesystem type. See the options flag
125 page and the filesystem specific page, such as
127 for additional options that may be specified.
129 If the options ``userquota'' and/or ``groupquota'' are specified,
130 the filesystem is automatically processed by the
132 command, and user and/or group disk quotas are enabled with
135 filesystem quotas are maintained in files named
139 which are located at the root of the associated filesystem.
140 These defaults may be overridden by putting an equal sign
141 and an alternative absolute pathname following the quota option.
142 Thus, if the user quota file for
145 .Pa /var/quotas/tmp.user ,
146 this location can be specified as:
147 .Bd -literal -offset indent
148 userquota=/var/quotas/tmp.user
151 If the option ``noauto'' is specified, the filesystem will not be automatically
152 mounted at system startup.
153 This is recommended for all remote filesystems other than NFS,
154 since only NFS mounts are delayed until after network initialization
159 The type of the mount is extracted from the
161 field and stored separately in the
163 field (it is not deleted from the
168 is ``rw'' or ``ro'' then the filesystem whose name is given in the
170 field is normally mounted read-write or read-only on the
171 specified special file.
174 is ``sw'' then the special file is made available as a piece of swap
177 command at the end of the system reboot procedure.
178 The fields other than
185 is specified as ``xx'' the entry is ignored.
186 This is useful to show disk partitions which are currently unused.
190 is used for these filesystems by the
192 command to determine which filesystems need to be dumped.
193 If the fifth field is not present, a value of zero is returned and
195 will assume that the filesystem does not need to be dumped.
201 program to determine the order in which filesystem checks are done
203 The root filesystem should be specified with a
205 of 1, and other filesystems should have a
208 Filesystems within a drive will be checked sequentially,
209 but filesystems on different drives will be checked at the
210 same time to utilize parallelism available in the hardware.
211 If the sixth field is not present or is zero,
212 a value of zero is returned and
214 will assume that the filesystem does not need to be checked.
216 #define FSTAB_RW "rw" /* read/write device */
217 #define FSTAB_RQ "rq" /* read/write with quotas */
218 #define FSTAB_RO "ro" /* read-only device */
219 #define FSTAB_SW "sw" /* swap device */
220 #define FSTAB_XX "xx" /* ignore totally */
223 char *fs_spec; /* block special device name */
224 char *fs_file; /* filesystem path prefix */
225 char *fs_vfstype; /* File system type, ufs, nfs */
226 char *fs_mntops; /* Mount options ala -o */
227 char *fs_type; /* FSTAB_* from fs_mntops */
228 int fs_freq; /* dump frequency, in days */
229 int fs_passno; /* pass number on parallel fsck */
233 The proper way to read records from
235 is to use the routines
242 .Bl -tag -width /etc/fstab -compact
262 file format appeared in