Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man4/vfstab.4
+++ new/usr/src/man/man4/vfstab.4
1 1 '\" te
2 2 .\" Copyright (c) 2001 Sun Microsystems, Inc. All Rights Reserved.
3 3 .\" Copyright 1989 AT&T
4 +.\" Copyright 2015 Nexenta Systems, Inc. All rights reserved.
4 5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 6 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 7 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 -.TH VFSTAB 4 "Mar 2, 2007"
8 +.TH VFSTAB 4 "Sep 8, 2015"
8 9 .SH NAME
9 10 vfstab \- table of file system defaults
10 11 .SH DESCRIPTION
11 12 .sp
12 13 .LP
13 14 The file \fB/etc/vfstab\fR describes defaults for each file system. The
14 15 information is stored in a table with the following column headings:
15 16 .sp
16 17 .in +2
17 18 .nf
18 19 device device mount FS fsck mount mount
19 20 to mount to fsck point type pass at boot options
20 21 .fi
21 22 .in -2
22 23 .sp
23 24
24 25 .sp
25 26 .LP
26 27 The fields in the table are space-separated and show the resource name
27 28 (\fIdevice to mount\fR), the raw device to \fBfsck\fR (\fIdevice to fsck\fR),
28 29 the default mount directory (\fImount point\fR), the name of the file system
29 30 type (\fIFS type\fR), the number used by \fBfsck\fR to decide whether to check
30 31 the file system automatically (\fIfsck pass\fR), whether the file system should
31 32 be mounted automatically by \fBmountall\fR (\fImount at boot\fR), and the file
32 33 system mount options (\fImount options\fR). (See respective mount file system
33 34 man page below in \fBSEE ALSO\fR for \fImount options\fR.) A '-' is used to
34 35 indicate no entry in a field. This may be used when a field does not apply to
35 36 the resource being mounted.
36 37 .sp
37 38 .LP
38 39 The \fBgetvfsent\fR(3C) family of routines is used to read and write to
39 40 \fB/etc/vfstab\fR.
40 41 .sp
41 42 .LP
42 43 \fB/etc/vfstab\fR can be used to specify swap areas. An entry so specified,
43 44 (which can be a file or a device), will automatically be added as a swap area
44 45 by the \fB/sbin/swapadd\fR script when the system boots. To specify a swap
45 46 area, the \fIdevice-to-mount\fR field contains the name of the swap file or
46 47 device, the \fIFS-type\fR is "swap", \fImount-at-boot\fR is "no" and all other
47 48 fields have no entry.
48 49 .SH EXAMPLES
49 50 .sp
50 51 .LP
51 52 The following are \fBvfstab\fR entries for various file system types supported
52 53 in the Solaris operating environment.
53 54 .LP
54 55 \fBExample 1 \fRNFS and UFS Mounts
55 56 .sp
56 57 .LP
57 58 The following entry invokes NFS to automatically mount the directory
58 59 \fB/usr/local\fR of the server \fBexample1\fR on the client's \fB/usr/local\fR
59 60 directory with read-only permission:
60 61
61 62 .sp
62 63 .in +2
63 64 .nf
64 65 example1:/usr/local - /usr/local nfs - yes ro
65 66 .fi
66 67 .in -2
67 68 .sp
68 69
69 70 .sp
70 71 .LP
71 72 The following example assumes a small departmental mail setup, in which clients
72 73 mount \fB/var/mail\fR from a server \fBmailsvr\fR. The following entry would be
73 74 listed in each client's \fBvfstab\fR:
74 75
75 76 .sp
76 77 .in +2
77 78 .nf
78 79 mailsvr:/var/mail - /var/mail nfs - yes intr,bg
79 80 .fi
80 81 .in -2
81 82 .sp
82 83
83 84 .sp
84 85 .LP
85 86 The following is an example for a UFS file system in which logging is enabled:
86 87
87 88 .sp
88 89 .in +2
89 90 .nf
90 91 /dev/dsk/c2t10d0s0 /dev/rdsk/c2t10d0s0 /export/local ufs 3 yes logging
91 92 .fi
92 93 .in -2
93 94 .sp
94 95
95 96 .sp
96 97 .LP
97 98 See \fBmount_nfs\fR(1M) for a description of NFS mount options and
98 99 \fBmount_ufs\fR(1M) for a description of UFS options.
99 100
100 101 .LP
101 102 \fBExample 2 \fR\fBpcfs\fR Mounts
102 103 .sp
103 104 .LP
104 105 The following example mounts a \fBpcfs\fR file system on a fixed hard disk on
105 106 an x86 machine:
106 107
107 108 .sp
108 109 .in +2
109 110 .nf
110 111 /dev/dsk/c1t2d0p0:c - /win98 pcfs - yes -
111 112 .fi
112 113 .in -2
113 114 .sp
114 115
115 116 .sp
116 117 .LP
117 118 The example below mounts a Jaz drive on a SPARC machine. Normally, the volume
118 119 management software handles mounting of removable media, obviating a
119 120 \fBvfstab\fR entry. Specifying a device that supports removable media in
120 121 \fBvfstab\fR with set the mount-at-boot field to \fBno\fR (as shown below)
121 122 disables the automatic handling of that device. Such an entry presumes you are
122 123 not running volume management software.
123 124
124 125 .sp
125 126 .in +2
126 127 .nf
127 128 /dev/dsk/c1t2d0s2:c - /jaz pcfs - no -
128 129 .fi
129 130 .in -2
130 131 .sp
131 132
132 133 .sp
133 134 .LP
134 135 For removable media on a SPARC machine, the convention for the slice portion of
|
↓ open down ↓ |
117 lines elided |
↑ open up ↑ |
135 136 the disk identifier is to specify \fBs2\fR, which stands for the entire medium.
136 137
137 138 .sp
138 139 .LP
139 140 For \fBpcfs\fR file systems on x86 machines, note that the disk identifier uses
140 141 a \fBp\fR (\fBp0\fR) and a logical drive (\fBc\fR, in the \fB/win98\fR example
141 142 above) for a \fBpcfs\fR logical drive. See \fBmount_pcfs\fR(1M) for syntax for
142 143 \fBpcfs\fR logical drives and for \fBpcfs\fR-specific mount options.
143 144
144 145 .LP
145 -\fBExample 3 \fRCacheFS Mount
146 +\fBExample 3 \fRLoopback File System Mount
146 147 .sp
147 148 .LP
148 -Below is an example for a CacheFS file system. Because of the length of this
149 -entry and the fact that \fBvfstab\fR entries cannot be continued to a second
150 -line, the \fBvfstab\fR fields are presented here in a vertical format. In
151 -re-creating such an entry in your own \fBvfstab\fR, you would enter values as
152 -you would for any \fBvfstab\fR entry, on a single line.
153 -
154 -.sp
155 -.in +2
156 -.nf
157 -device to mount: svr1:/export/abc
158 -device to fsck: /usr/abc
159 -mount point: /opt/cache
160 -FS type: cachefs
161 -fsck pass: 7
162 -mount at boot: yes
163 -mount options:
164 -local-access,bg,nosuid,demandconst,backfstype=nfs,cachedir=/opt/cache
165 -.fi
166 -.in -2
167 -.sp
168 -
169 -.sp
170 -.LP
171 -See \fBmount_cachefs\fR(1M) for CacheFS-specific mount options.
172 -
173 -.LP
174 -\fBExample 4 \fRLoopback File System Mount
175 -.sp
176 -.LP
177 149 The following is an example of mounting a loopback (\fBlofs\fR) file system:
178 150
179 151 .sp
180 152 .in +2
181 153 .nf
182 154 /export/test - /opt/test lofs - yes -
183 155 .fi
184 156 .in -2
185 157 .sp
186 158
187 159 .sp
188 160 .LP
189 161 See \fBlofs\fR(7FS) for an overview of the loopback file system.
190 162
191 163 .SH SEE ALSO
192 164 .sp
193 165 .LP
194 -\fBfsck\fR(1M), \fBmount\fR(1M), \fBmount_cachefs\fR(1M), \fBmount_hsfs\fR(1M),
166 +\fBfsck\fR(1M), \fBmount\fR(1M), \fBmount_hsfs\fR(1M),
195 167 \fBmount_nfs\fR(1M), \fBmount_tmpfs\fR(1M), \fBmount_ufs\fR(1M),
196 168 \fBswap\fR(1M), \fBgetvfsent\fR(3C)
197 169 .sp
198 170 .LP
199 171 \fISystem Administration Guide: Basic Administration\fR
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX