1mount_ufs(1M) System Administration Commands mount_ufs(1M)
2
6 mount_ufs - mount ufs file systems
7
9 mount -F ufs [generic_options] [-o specific_options]
10 [-O] special | mount_point
11 mount -F ufs [generic_options] [-o specific_options]
14 [-O] special mount_point
15
18 The mount utility attaches a ufs file system to the file system hierar‐
19 chy at the mount_point, which is the pathname of a directory. If
20 mount_point has any contents prior to the mount operation, these are
21 hidden until the file system is unmounted.
22 The ufs file system supports direct mounting of files containing the
25 file system as well as block devices. See mount(1M) and lofiadm(1M).
26 If mount is invoked with special or mount_point as the only arguments,
29 mount will search /etc/vfstab to fill in the missing arguments, includ‐
30 ing the specific_options. See mount(1M).
31 If special and mount_point are specified without any specific_options,
34 the default is rw.
35 If the directory on which a file system is to be mounted is a symbolic
38 link, the file system is mounted on the directory to which the symbolic
39 link refers, rather than on top of the symbolic link itself.
40
42 See mount(1M) for the list of supported generic_options.
43 The following options are supported:
46 -o specific_options
48 Specify ufs file system specific options in a comma-separated list
50 with no intervening spaces. If invalid options are specified, a
51 warning message is printed and the invalid options are ignored. The
52 following options are available:
53 dfratime | nodfratime
55 By default, writing access time updates to the disk may be
57 deferred (dfratime) for the file system until the disk is
58 accessed for a reason other than updating access times. nod‐
59 fratime disables this behavior.
60 If power management is enabled on the system, do not set nod‐
62 fratime unless noatime is also set. If you set nodfratime with‐
63 out setting noatime, the disk is spun up every time a file
64 within a file system on the disk is accessed - even if the file
65 is not modified.
66 forcedirectio | noforcedirectio
69 If forcedirectio is specified and supported by the file system,
71 then for the duration of the mount, forced direct I/O will be
72 used. If the filesystem is mounted using forcedirectio, data is
73 transferred directly between user address space and the disk.
74 If the filesystem is mounted using noforcedirectio, data is
75 buffered in kernel address space when data is transferred
76 between user address space and the disk. forcedirectio is a
77 performance option that is of benefit only in large sequential
78 data transfers. The default behavior is noforcedirectio.
79 global | noglobal
82 If global is specified and supported on the file system, and
84 the system in question is part of a cluster, the file system
85 will be globally visible on all nodes of the cluster. If
86 noglobal is specified, the mount will not be globally visible.
87 The default behavior is noglobal.
88 intr | nointr
91 Allow (do not allow) keyboard interrupts to kill a process that
93 is waiting for an operation on a locked file system. The
94 default is intr.
95 largefiles | nolargefiles
98 If nolargefiles is specified and supported by the file system,
100 then for the duration of the mount it is guaranteed that all
101 regular files in the file system have a size that will fit in
102 the smallest object of type off_t supported by the system per‐
103 forming the mount. The mount will fail if there are any files
104 in the file system not meeting this criterion. If largefiles is
105 specified, there is no such guarantee. The default behavior is
106 largefiles.
107 If nolargefiles is specified, mount will fail for ufs if the
109 file system to be mounted has contained a large file (a file
110 whose size is greater than or equal to 2 Gbyte) since the last
111 invocation of fsck on the file system. The large file need not
112 be present in the file system at the time of the mount for the
113 mount to fail; it could have been created previously and
114 destroyed. Invoking fsck (see fsck_ufs(1M)) on the file system
115 will reset the file system state if no large files are present.
116 After invoking fsck, a successful mount of the file system with
117 nolargefiles specified indicates the absence of large files in
118 the file system; an unsuccessful mount attempt indicates the
119 presence of at least one large file.
120 logging | nologging
123 If logging is specified, then logging is enabled for the dura‐
125 tion of the mounted file system. Logging is the process of
126 storing transactions (changes that make up a complete UFS oper‐
127 ation) in a log before the transactions are applied to the file
128 system. Once a transaction is stored, the transaction can be
129 applied to the file system later. This prevents file systems
130 from becoming inconsistent, therefore reducing the possibility
131 that fsck might run. And, if fsck is bypassed, logging gener‐
132 ally reduces the time required to reboot a system.
133 The default behavior is logging for all UFS file systems.
135 The log is allocated from free blocks in the file system, and
137 is sized approximately 1 Mbyte per 1 Gbyte of file system, up
138 to a maximum of 256 Mbytes. The log size may be larger (up to a
139 maximum of 512 Mbytes) dependent upon the number of cylinder
140 groups present in the file system.
141 Logging is enabled on any UFS file system, including root (/),
143 except under the following conditions:
144 o When logging is specifically disabled.
146 o If there is insufficient file system space for the
148 log. In this case, the following message is dis‐
149 played and file system is still mounted:
150 # mount /dev/dsk/c0t4d0s0 /mnt
152 /mnt: No space left on device
153 Could not enable logging for /mnt on /dev/dsk/c0t4d0s0.
154 The log created by UFS logging is continually flushed as it
157 fills up. The log is totally flushed when the file system is
158 unmounted or as a result of the lockfs -f command.
159 m
162 Mount the file system without making an entry in /etc/mnttab.
164 noatime
167 By default, the file system is mounted with normal access time
169 (atime) recording. If noatime is specified, the file system
170 will ignore access time updates on files, except when they
171 coincide with updates to the ctime or mtime. See stat(2). This
172 option reduces disk activity on file systems where access times
173 are unimportant (for example, a Usenet news spool).
174 noatime turns off access time recording regardless of dfratime
176 or nodfratime.
177 The POSIX standard requires that access times be marked on
179 files. -noatime ignores them unless the file is also modified.
180 nosec
183 By default, Access Control Lists (ACLs) are supported on a
185 mounted UFS file system. Use this option to disallow the set‐
186 ting or any modification of an ACL on a file within a mounted
187 UFS file system. See getfacl(1) for background on ACLs.
188 onerror = action
191 This option specifies the action that UFS should take to
193 recover from an internal inconsistency on a file system. Spec‐
194 ify action as panic, lock, or umount. These values cause a
195 forced system shutdown, a file system lock to be applied to the
196 file system, or the file system to be forcibly unmounted,
197 respectively. The default is panic.
198 quota
201 Quotas are turned on for the file system.
203 remount
206 Remounts a file system with a new set of options. All options
208 not explicitly set with remount revert to their default values.
209 rq
212 Read-write with quotas turned on. Equivalent to rw, quota.
214 xattr | noxattr
218 Allow or disallow the creation and manipulation of extended
220 attributes. The default is xattr. See fsattr(5) for a description
221 of extended attributes.
222 -O
225 Overlay mount. Allow the file system to be mounted over an existing
227 mount point, making the underlying file system inaccessible. If a
228 mount is attempted on a pre-existing mount point without setting
229 this flag, the mount will fail, producing the error "device busy".
230
233 Example 1 Turning Off (and On) Logging
234 The following command turns off logging on an already mounted file sys‐
237 tem. The subsequent command restores logging.
238 # mount -F ufs -o remount,nologging /export
241 # (absence of message indicates success)
242 # mount -F ufs -o remount,logging /export
243 In the preceding commands, the -F ufs option is not necessary.
247
250 /etc/mnttab
251 table of mounted file systems
253 /etc/vfstab
256 list of default parameters for each file system
258
261 See attributes(5) for descriptions of the following attributes:
262 ┌─────────────────────────────┬─────────────────────────────┐
267 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
268 ├─────────────────────────────┼─────────────────────────────┤
269 │Availability │SUNWcsu │
270 └─────────────────────────────┴─────────────────────────────┘
271
273 getfacl(1), fsck(1M), fsck_ufs(1M), lofiadm(1M), mount(1M), moun‐
274 tall(1M), fcntl(2), mount(2), stat(2), mnttab(4), vfstab(4),
275 attributes(5), fsattr(5), largefile(5)
276
278 Since the root (/) file system is mounted read-only by the kernel dur‐
279 ing the boot process, only the remount option (and options that can be
280 used in conjunction with remount) affect the root (/) entry in the
281 /etc/vfstab file.
282SunOS 5.11 22 Jun 2009 mount_ufs(1M)