Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man4/vfstab.4.man.txt
+++ new/usr/src/man/man4/vfstab.4.man.txt
1 1 VFSTAB(4) File Formats VFSTAB(4)
2 2
3 3
4 4
5 5 NAME
6 6 vfstab - table of file system defaults
7 7
8 8 DESCRIPTION
9 9 The file /etc/vfstab describes defaults for each file system. The
10 10 information is stored in a table with the following column headings:
11 11
12 12 device device mount FS fsck mount mount
13 13 to mount to fsck point type pass at boot options
14 14
15 15
16 16
17 17
18 18 The fields in the table are space-separated and show the resource name
19 19 (device to mount), the raw device to fsck (device to fsck), the default
20 20 mount directory (mount point), the name of the file system type (FS
21 21 type), the number used by fsck to decide whether to check the file
22 22 system automatically (fsck pass), whether the file system should be
23 23 mounted automatically by mountall (mount at boot), and the file system
24 24 mount options (mount options). (See respective mount file system man
25 25 page below in SEE ALSO for mount options.) A '-' is used to indicate no
26 26 entry in a field. This may be used when a field does not apply to the
27 27 resource being mounted.
28 28
29 29
30 30 The getvfsent(3C) family of routines is used to read and write to
31 31 /etc/vfstab.
32 32
33 33
34 34 /etc/vfstab can be used to specify swap areas. An entry so specified,
35 35 (which can be a file or a device), will automatically be added as a
36 36 swap area by the /sbin/swapadd script when the system boots. To specify
37 37 a swap area, the device-to-mount field contains the name of the swap file
38 38 or device, the FS-type is "swap", mount-at-boot is "no" and all other
39 39 fields have no entry.
40 40
41 41 EXAMPLES
42 42 The following are vfstab entries for various file system types
43 43 supported in the Solaris operating environment.
44 44
45 45 Example 1 NFS and UFS Mounts
46 46
47 47
48 48 The following entry invokes NFS to automatically mount the directory
49 49 /usr/local of the server example1 on the client's /usr/local directory
50 50 with read-only permission:
51 51
52 52
53 53 example1:/usr/local - /usr/local nfs - yes ro
54 54
55 55
56 56
57 57
58 58 The following example assumes a small departmental mail setup, in which
59 59 clients mount /var/mail from a server mailsvr. The following entry
60 60 would be listed in each client's vfstab:
61 61
62 62
63 63 mailsvr:/var/mail - /var/mail nfs - yes intr,bg
64 64
65 65
66 66
67 67
68 68 The following is an example for a UFS file system in which logging is
69 69 enabled:
70 70
71 71
72 72 /dev/dsk/c2t10d0s0 /dev/rdsk/c2t10d0s0 /export/local ufs 3 yes logging
73 73
74 74
75 75
76 76
77 77 See mount_nfs(1M) for a description of NFS mount options and
78 78 mount_ufs(1M) for a description of UFS options.
79 79
80 80
81 81 Example 2 pcfs Mounts
82 82
83 83
84 84 The following example mounts a pcfs file system on a fixed hard disk on
85 85 an x86 machine:
86 86
87 87
88 88 /dev/dsk/c1t2d0p0:c - /win98 pcfs - yes -
89 89
90 90
91 91
92 92
93 93 The example below mounts a Jaz drive on a SPARC machine. Normally, the
94 94 volume management software handles mounting of removable media,
95 95 obviating a vfstab entry. Specifying a device that supports removable
96 96 media in vfstab with set the mount-at-boot field to no (as shown below)
97 97 disables the automatic handling of that device. Such an entry presumes
98 98 you are not running volume management software.
99 99
100 100
101 101 /dev/dsk/c1t2d0s2:c - /jaz pcfs - no -
102 102
103 103
104 104
105 105
106 106 For removable media on a SPARC machine, the convention for the slice
107 107 portion of the disk identifier is to specify s2, which stands for the
|
↓ open down ↓ |
107 lines elided |
↑ open up ↑ |
108 108 entire medium.
109 109
110 110
111 111
112 112 For pcfs file systems on x86 machines, note that the disk identifier
113 113 uses a p (p0) and a logical drive (c, in the /win98 example above) for
114 114 a pcfs logical drive. See mount_pcfs(1M) for syntax for pcfs logical
115 115 drives and for pcfs-specific mount options.
116 116
117 117
118 - Example 3 CacheFS Mount
118 + Example 3 Loopback File System Mount
119 119
120 120
121 - Below is an example for a CacheFS file system. Because of the length of
122 - this entry and the fact that vfstab entries cannot be continued to a
123 - second line, the vfstab fields are presented here in a vertical format.
124 - In re-creating such an entry in your own vfstab, you would enter values
125 - as you would for any vfstab entry, on a single line.
126 -
127 -
128 - device to mount: svr1:/export/abc
129 - device to fsck: /usr/abc
130 - mount point: /opt/cache
131 - FS type: cachefs
132 - fsck pass: 7
133 - mount at boot: yes
134 - mount options:
135 - local-access,bg,nosuid,demandconst,backfstype=nfs,cachedir=/opt/cache
136 -
137 -
138 -
139 -
140 - See mount_cachefs(1M) for CacheFS-specific mount options.
141 -
142 -
143 - Example 4 Loopback File System Mount
144 -
145 -
146 121 The following is an example of mounting a loopback (lofs) file system:
147 122
148 123
149 124 /export/test - /opt/test lofs - yes -
150 125
151 126
152 127
153 128
154 129 See lofs(7FS) for an overview of the loopback file system.
155 130
156 131
157 132 SEE ALSO
158 - fsck(1M), mount(1M), mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M),
159 - mount_tmpfs(1M), mount_ufs(1M), swap(1M), getvfsent(3C)
133 + fsck(1M), mount(1M), mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M),
134 + mount_ufs(1M), swap(1M), getvfsent(3C)
160 135
161 136
162 137 System Administration Guide: Basic Administration
163 138
164 139
165 140
166 - March 2, 2007 VFSTAB(4)
141 + September 8, 2015 VFSTAB(4)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX