| blob | e910b7f87f88040346c774e403b8125927d13faa |
1 '\" te
2 .\" Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved
3 .\" Copyright 1989 AT&T
4 .\" 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. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
5 .\" See the License for the specific language governing permissions and limitations under the License. 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
6 .\" the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH MOUNT_UFS 1M "Jun 22, 2009"
8 .SH NAME
9 mount_ufs \- mount ufs file systems
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fBmount\fR \fB-F\fR ufs [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR]
14 [\fB-O\fR] \fIspecial\fR | \fImount_point\fR
15 .fi
17 .LP
18 .nf
19 \fBmount\fR \fB-F\fR ufs [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR]
20 [\fB-O\fR] \fIspecial\fR \fImount_point\fR
21 .fi
23 .SH DESCRIPTION
24 .sp
25 .LP
26 The \fBmount\fR utility attaches a \fBufs\fR file system to the file system
27 hierarchy at the \fImount_point\fR, which is the pathname of a directory. If
28 \fImount_point\fR has any contents prior to the \fBmount\fR operation, these
29 are hidden until the file system is unmounted.
30 .sp
31 .LP
32 The \fBufs\fR file system supports direct mounting of files containing the file
33 system as well as block devices. See \fBmount\fR(1M) and \fBlofiadm\fR(1M).
34 .sp
35 .LP
36 If \fBmount\fR is invoked with \fIspecial\fR or \fImount_point\fR as the only
37 arguments, \fBmount\fR will search \fB/etc/vfstab\fR to fill in the missing
38 arguments, including the \fIspecific_options\fR. See \fBmount\fR(1M).
39 .sp
40 .LP
41 If \fIspecial\fR and \fImount_point\fR are specified without any
42 \fIspecific_options\fR, the default is \fBrw\fR.
43 .sp
44 .LP
45 If the directory on which a file system is to be mounted is a symbolic link,
46 the file system is mounted on the directory to which the symbolic link refers,
47 rather than on top of the symbolic link itself.
48 .SH OPTIONS
49 .sp
50 .LP
51 See \fBmount\fR(1M) for the list of supported \fIgeneric_options\fR.
52 .sp
53 .LP
54 The following options are supported:
55 .sp
56 .ne 2
57 .na
58 \fB\fB-o\fR \fIspecific_options\fR\fR
59 .ad
60 .sp .6
61 .RS 4n
62 Specify \fBufs\fR file system specific options in a comma-separated list with
63 no intervening spaces. If invalid options are specified, a warning message is
64 printed and the invalid options are ignored. The following options are
65 available:
66 .sp
67 .ne 2
68 .na
69 \fB\fBdfratime\fR | \fBnodfratime\fR\fR
70 .ad
71 .sp .6
72 .RS 4n
73 By default, writing access time updates to the disk may be deferred
74 (\fBdfratime\fR) for the file system until the disk is accessed for a reason
75 other than updating access times. \fBnodfratime\fR disables this behavior.
76 .sp
77 If power management is enabled on the system, do not set \fBnodfratime\fR
78 unless \fBnoatime\fR is also set. If you set \fBnodfratime\fR without setting
79 \fBnoatime\fR, the disk is spun up every time a file within a file system on
80 the disk is accessed - even if the file is not modified.
81 .RE
83 .sp
84 .ne 2
85 .na
86 \fB\fBforcedirectio\fR | \fBnoforcedirectio\fR\fR
87 .ad
88 .sp .6
89 .RS 4n
90 If \fBforcedirectio\fR is specified and supported by the file system, then for
91 the duration of the mount, forced direct \fBI/O\fR will be used. If the
92 filesystem is mounted using \fBforcedirectio\fR, data is transferred directly
93 between user address space and the disk. If the filesystem is mounted using
94 \fBnoforcedirectio\fR, data is buffered in kernel address space when data is
95 transferred between user address space and the disk. \fBforcedirectio\fR is a
96 performance option that is of benefit only in large sequential data transfers.
97 The default behavior is \fBnoforcedirectio\fR.
98 .RE
100 .sp
101 .ne 2
102 .na
103 \fB\fBglobal\fR | \fBnoglobal\fR\fR
104 .ad
105 .sp .6
106 .RS 4n
107 If \fBglobal\fR is specified and supported on the file system, and the system
108 in question is part of a cluster, the file system will be globally visible on
109 all nodes of the cluster. If \fBnoglobal\fR is specified, the mount will not be
110 globally visible. The default behavior is \fBnoglobal\fR.
111 .RE
113 .sp
114 .ne 2
115 .na
116 \fB\fBintr\fR | \fBnointr\fR\fR
117 .ad
118 .sp .6
119 .RS 4n
120 Allow (do not allow) keyboard interrupts to kill a process that is waiting for
121 an operation on a locked file system. The default is \fBintr\fR.
122 .RE
124 .sp
125 .ne 2
126 .na
127 \fB\fBlargefiles\fR | \fBnolargefiles\fR\fR
128 .ad
129 .sp .6
130 .RS 4n
131 If \fBnolargefiles\fR is specified and supported by the file system, then for
132 the duration of the mount it is guaranteed that all regular files in the file
133 system have a size that will fit in the smallest object of type \fBoff_t\fR
134 supported by the system performing the mount. The mount will fail if there are
135 any files in the file system not meeting this criterion. If \fBlargefiles\fR is
136 specified, there is no such guarantee. The default behavior is
137 \fBlargefiles\fR.
138 .sp
139 If \fBnolargefiles\fR is specified, \fBmount\fR will fail for \fBufs\fR if the
140 file system to be mounted has contained a large file (a file whose size is
141 greater than or equal to 2 Gbyte) since the last invocation of \fBfsck\fR on
142 the file system. The large file need not be present in the file system at the
143 time of the mount for the mount to fail; it could have been created previously
144 and destroyed. Invoking \fBfsck\fR (see \fBfsck_ufs\fR(1M)) on the file system
145 will reset the file system state if no large files are present. After invoking
146 \fBfsck\fR, a successful mount of the file system with \fBnolargefiles\fR
147 specified indicates the absence of large files in the file system; an
148 unsuccessful mount attempt indicates the presence of at least one large file.
149 .RE
151 .sp
152 .ne 2
153 .na
154 \fB\fBlogging\fR | \fBnologging\fR\fR
155 .ad
156 .sp .6
157 .RS 4n
158 If \fBlogging\fR is specified, then logging is enabled for the duration of the
159 mounted file system. Logging is the process of storing transactions (changes
160 that make up a complete \fBUFS\fR operation) in a log before the transactions
161 are applied to the file system. Once a transaction is stored, the transaction
162 can be applied to the file system later. This prevents file systems from
163 becoming inconsistent, therefore reducing the possibility that \fBfsck\fR
164 might run. And, if \fBfsck\fR is bypassed, logging generally reduces the time
165 required to reboot a system.
166 .sp
167 The default behavior is \fBlogging\fR for all UFS file systems.
168 .sp
169 The log is allocated from free blocks in the file system, and is sized
170 approximately 1 Mbyte per 1 Gbyte of file system, up to a maximum of 256
171 Mbytes. The log size may be larger (up to a maximum of 512 Mbytes) dependent
172 upon the number of cylinder groups present in the file system.
173 .sp
174 Logging is enabled on any \fBUFS\fR file system, including root (\fB/\fR),
175 except under the following conditions:
176 .RS +4
177 .TP
178 .ie t \(bu
179 .el o
180 When logging is specifically disabled.
181 .RE
182 .RS +4
183 .TP
184 .ie t \(bu
185 .el o
186 If there is insufficient file system space for the log. In this case, the
187 following message is displayed and file system is still mounted:
188 .sp
189 .in +2
190 .nf
191 # mount /dev/dsk/c0t4d0s0 /mnt
192 /mnt: No space left on device
193 Could not enable logging for /mnt on /dev/dsk/c0t4d0s0.
194 .fi
195 .in -2
196 .sp
198 .RE
199 The log created by \fBUFS\fR logging is continually flushed as it fills up. The
200 log is totally flushed when the file system is unmounted or as a result of the
201 \fBlockfs -f\fR command.
202 .RE
204 .sp
205 .ne 2
206 .na
207 \fB\fBm\fR\fR
208 .ad
209 .sp .6
210 .RS 4n
211 Mount the file system without making an entry in \fB/etc/mnttab\fR.
212 .RE
214 .sp
215 .ne 2
216 .na
217 \fB\fBnoatime\fR\fR
218 .ad
219 .sp .6
220 .RS 4n
221 By default, the file system is mounted with normal access time (\fBatime\fR)
222 recording. If \fBnoatime\fR is specified, the file system will ignore access
223 time updates on files, except when they coincide with updates to the
224 \fBctime\fR or \fBmtime\fR. See \fBstat\fR(2). This option reduces disk
225 activity on file systems where access times are unimportant (for example, a
226 Usenet news spool).
227 .sp
228 \fBnoatime\fR turns off access time recording regardless of \fBdfratime\fR or
229 \fBnodfratime\fR.
230 .sp
231 The POSIX standard requires that access times be marked on files.
232 \fB-noatime\fR ignores them unless the file is also modified.
233 .RE
235 .sp
236 .ne 2
237 .na
238 \fB\fBnosec\fR\fR
239 .ad
240 .sp .6
241 .RS 4n
242 By default, Access Control Lists (ACLs) are supported on a mounted UFS file
243 system. Use this option to disallow the setting or any modification of an ACL
244 on a file within a mounted UFS file system. See \fBgetfacl\fR(1) for background
245 on ACLs.
246 .RE
248 .sp
249 .ne 2
250 .na
251 \fB\fBonerror\fR = \fIaction\fR\fR
252 .ad
253 .sp .6
254 .RS 4n
255 This option specifies the action that \fBUFS\fR should take to recover from an
256 internal inconsistency on a file system. Specify \fIaction\fR as \fBpanic\fR,
257 \fBlock\fR, or \fBumount\fR. These values cause a forced system shutdown, a
258 file system lock to be applied to the file system, or the file system to be
259 forcibly unmounted, respectively. The default is \fBpanic\fR.
260 .RE
262 .sp
263 .ne 2
264 .na
265 \fB\fBquota\fR\fR
266 .ad
267 .sp .6
268 .RS 4n
269 Quotas are turned on for the file system.
270 .RE
272 .sp
273 .ne 2
274 .na
275 \fB\fBremount\fR\fR
276 .ad
277 .sp .6
278 .RS 4n
279 Remounts a file system with a new set of options. All options not explicitly
280 set with \fBremount\fR revert to their default values.
281 .RE
283 .sp
284 .ne 2
285 .na
286 \fB\fBrq\fR\fR
287 .ad
288 .sp .6
289 .RS 4n
290 Read-write with quotas turned on. Equivalent to \fBrw, quota\fR.
291 .RE
293 .RE
295 .sp
296 .ne 2
297 .na
298 \fB\fBxattr\fR | \fBnoxattr\fR\fR
299 .ad
300 .sp .6
301 .RS 4n
302 Allow or disallow the creation and manipulation of extended attributes. The
303 default is \fBxattr\fR. See \fBfsattr\fR(5) for a description of extended
304 attributes.
305 .RE
307 .sp
308 .ne 2
309 .na
310 \fB\fB-O\fR\fR
311 .ad
312 .sp .6
313 .RS 4n
314 Overlay mount. Allow the file system to be mounted over an existing mount
315 point, making the underlying file system inaccessible. If a mount is attempted
316 on a pre-existing mount point without setting this flag, the mount will fail,
317 producing the error "device busy".
318 .RE
320 .SH EXAMPLES
321 .LP
322 \fBExample 1 \fRTurning Off (and On) Logging
323 .sp
324 .LP
325 The following command turns off logging on an already mounted file system. The
326 subsequent command restores logging.
328 .sp
329 .in +2
330 .nf
331 # mount -F ufs -o remount,nologging /export
332 # \fB(absence of message indicates success)\fR
333 # mount -F ufs -o remount,logging /export
334 .fi
335 .in -2
337 .sp
338 .LP
339 In the preceding commands, the \fB-F\fR \fBufs\fR option is not necessary.
341 .SH FILES
342 .sp
343 .ne 2
344 .na
345 \fB\fB/etc/mnttab\fR\fR
346 .ad
347 .sp .6
348 .RS 4n
349 table of mounted file systems
350 .RE
352 .sp
353 .ne 2
354 .na
355 \fB\fB/etc/vfstab\fR\fR
356 .ad
357 .sp .6
358 .RS 4n
359 list of default parameters for each file system
360 .RE
362 .SH SEE ALSO
363 .sp
364 .LP
365 \fBgetfacl\fR(1), \fBfsck\fR(1M), \fBfsck_ufs\fR(1M), \fBlofiadm\fR(1M),
366 \fBmount\fR(1M), \fBmountall\fR(1M), \fBfcntl\fR(2), \fBmount\fR(2),
367 \fBstat\fR(2), \fBmnttab\fR(4), \fBvfstab\fR(4), \fBattributes\fR(5),
368 \fBfsattr\fR(5), \fBlargefile\fR(5)
369 .SH NOTES
370 .sp
371 .LP
372 Since the root (\fB/\fR) file system is mounted read-only by the kernel during
373 the boot process, only the \fBremount\fR option (and options that can be used
374 in conjunction with \fBremount\fR) affect the root (\fB/\fR) entry in the
375 \fB/etc/vfstab\fR file.