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
40 .Nd static information about the file systems
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 file system 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 special device or
68 remote file system to be mounted.
69 The contents are decoded by the
72 This allows using spaces or tabs in the device name which would be
73 interpreted as field separators otherwise.
77 describes the mount point for the file system.
78 For swap partitions, this field should be specified as
80 The contents are decoded by the
86 describes the type of the file system.
87 The system can support various file system types.
88 Only the root, /usr, and /tmp file systems need be statically
89 compiled into the kernel;
90 everything else will be automatically loaded at mount
92 (Exception: the FFS cannot currently be demand-loaded.)
93 Some people still prefer to statically
94 compile other file systems as well.
98 describes the mount options associated with the file system.
99 It is formatted as a comma separated list of options.
100 It contains at least the type of mount (see
102 below) plus any additional options appropriate to the file system type.
107 page and the file system specific page, such as
109 for additional options that may be specified.
110 All options that can be given to the file system specific mount commands
114 They just need to be formatted a bit differently.
117 option can be used without the preceding
120 Other options need both the file system specific flag and its argument,
121 separated by an equal sign.
122 For example, mounting an
124 filesystem, the options
125 .Bd -literal -offset indent
126 -o sync -o noatime -m 644 -M 755 -u foo -g bar
130 .Bd -literal -offset indent
131 sync,noatime,-m=644,-M=755,-u=foo,-g=bar
134 in the option field of
142 the file system is automatically processed by the
144 command, and user and/or group disk quotas are enabled with
147 file system quotas are maintained in files named
151 which are located at the root of the associated file system.
152 These defaults may be overridden by putting an equal sign
153 and an alternative absolute pathname following the quota option.
154 Thus, if the user quota file for
157 .Pa /var/quotas/tmp.user ,
158 this location can be specified as:
159 .Bd -literal -offset indent
160 userquota=/var/quotas/tmp.user
166 the system will ignore any error which happens during the mount of that filesystem,
167 which would otherwise cause the system to drop into single user mode.
168 This option is implemented by the
170 command and will not be passed to the kernel.
174 is specified, the file system will not be automatically
175 mounted at system startup.
176 Note that, for network file systems
178 (i.e., types supported by additional software
179 not included in the base system)
180 to be automatically mounted at system startup,
182 .Va extra_netfs_types
184 variable must be used to extend the
186 startup script's list of network file system types.
190 is specified, the file system will be automatically mounted
191 at a stage of system startup after remote mount points are mounted.
192 For more detail about this option,
197 The type of the mount is extracted from the
199 field and stored separately in the
201 field (it is not deleted from the
210 then the file system whose name is given in the
212 field is normally mounted read-write or read-only on the
213 specified special file.
219 then the special file is made available as a piece of swap
222 command at the end of the system reboot procedure.
223 For vnode-backed swap spaces,
233 .Pq Do md Dc or Do md[0-9]* Dc
240 device is created with the specified file used as backing store,
241 and then the new device is used as swap space.
244 devices will cause automatic creation of encrypted devices.
251 options may be passed to control those
254 The fields other than
263 the entry is ignored.
264 This is useful to show disk partitions which are currently unused.
268 is used for these file systems by the
270 command to determine which file systems need to be dumped.
271 If the fifth field is not present, a value of zero is returned and
273 will assume that the file system does not need to be dumped.
274 If the fifth field is greater than 0, then it specifies the number of days
275 between dumps for this file system.
283 programs to determine the order in which file system and quota
284 checks are done at reboot time.
287 field can be any value between 0 and
290 The root file system should be specified with a
292 of 1, and other file systems should have a
297 value of 1 is always checked sequentially and be completed before
298 another file system is processed, and it will be processed before
299 all file systems with a larger
302 For any given value of
304 file systems within a drive will be checked sequentially,
305 but file systems on different drives will be checked at the
306 same time to utilize parallelism available in the hardware.
307 Once all file system checks are complete for the current
309 the same process will start over for the next
312 If the sixth field is not present or is zero,
313 a value of zero is returned and
317 will assume that the file system does not need to be checked.
321 field can be used to implement finer control when
322 the system utilities may determine that the file system resides
323 on a different physical device, when it actually does not, as with a
326 All file systems with a lower
328 value will be completed before starting on file systems with a
332 E.g. all file systems with a
334 of 2 will be completed before any file systems with a
336 of 3 or greater are started.
337 Gaps are allowed between the different
340 E.g. file systems listed in
344 values such as 0, 1, 2, 15, 100, 200, 300, and may appear in any order
348 #define FSTAB_RW "rw" /* read/write device */
349 #define FSTAB_RQ "rq" /* read/write with quotas */
350 #define FSTAB_RO "ro" /* read-only device */
351 #define FSTAB_SW "sw" /* swap device */
352 #define FSTAB_XX "xx" /* ignore totally */
355 char *fs_spec; /* block special device name */
356 char *fs_file; /* file system path prefix */
357 char *fs_vfstype; /* File system type, ufs, nfs */
358 char *fs_mntops; /* Mount options ala -o */
359 char *fs_type; /* FSTAB_* from fs_mntops */
360 int fs_freq; /* dump frequency, in days */
361 int fs_passno; /* pass number on parallel fsck */
365 The proper way to read records from
367 is to use the routines
374 .Bl -tag -width /etc/fstab -compact
383 # Device Mountpoint FStype Options Dump Pass#
386 /dev/da0p2 / ufs rw 1 1
388 # Swap space on a block device.
389 /dev/da0p1 none swap sw 0 0
391 # Swap space using a block device with GBDE/GELI encyption.
392 # aalgo, ealgo, keylen, sectorsize options are available
394 /dev/da1p1.bde none swap sw 0 0
395 /dev/da1p2.eli none swap sw 0 0
398 tmpfs /tmp tmpfs rw,size=1g,mode=1777 0 0
400 # UFS file system on a swap-backed md(4). /dev/md10 is
401 # automatically created. If it is "md", a unit number
402 # will be automatically selected.
403 md10 /scratch mfs rw,-s1g 0 0
405 # Swap space on a vnode-backed md(4).
406 md11 none swap sw,file=/swapfile 0 0
408 # CDROM. "noauto" option is typically used because the
409 # media is removable.
410 /dev/cd0 /cdrom cd9660 ro,noauto 0 0
412 # NFS-exported file system. "serv" is an NFS server name
414 serv:/export /nfs nfs rw,noinet6 0 0
432 file format appeared in