1mount.ocfs2(8) OCFS2 Manual Pages mount.ocfs2(8)
2
6 mount.ocfs2 - mount an OCFS2 filesystem
7
9 mount.ocfs2 [-vn] [-o options] device dir
10
12 mount.ocfs2 mounts an OCFS2 filesystem at dir. It is usually invoked
13 indirectly by the mount(8) command.
14
17 _netdev
18 Indicates that the file system resides on a device that requires
19 network access (used to prevent the system from attempting to
20 mount these filesystems until the network has been enabled on
21 the system). mount.ocfs2(8) transparently appends this option
22 during mount. However, users mounting the volume via /etc/fstab
23 must explicitly specify this mount option to delay the system
24 from mounting the volume until after the network has been
25 enabled.
26 noatime
29 The file system will not update access time.
30 relatime
33 The file system will update atime only if the on-disk atime is
34 older than mtime or ctime.
35 strictatime,atime_quantum=nrsec
38 The file system will always perform atime updates, but the mini‐
39 mum update interval is specified by atime_quantum which defaults
40 to 60 secs. Set it to zero to always update atime. These two
41 options need work together.
42 [no]acl
45 Enables / disables POSIX ACLs (access control lists) support.
46 [no]user_xattr
49 Enables / disables extended user attributes.
50 commit=nrsec
53 Sync all data and metadata every nrsec seconds. The default
54 value is 5 seconds. Zero means default.
55 data=[ordered|writeback]
58 Specifies the handling of file data during metadata journalling.
59 ordered
62 This is the default mode. Data is flushed to disk before
63 the corresponding meta-data is committed to the journal.
64 writeback
67 Data ordering is not preserved - data may be flushed to
68 disk after the corresponding meta-data is committed to
69 the journal. This is rumored to be the higher-throughput
70 option. While it guarantees internal file system
71 integrity, it can allow old data to appear in files after
72 a crash and journal recovery.
73 errors=[remount-ro|errors=panic|errors=continue]
76 Specifies the behavior when an on-disk corruption is encoun‐
77 tered.
78 remount-ro
81 This is the default mode. The file system is remounted
82 read-only.
83 panic The system is halted via panic.
86 continue
89 Ignore errors. Just log error message, return error code
90 to the calling process and continue.
91 localflocks
94 This disables cluster-aware flock(2).
95 coherency=[full|coherency]
98 Specifies the extent of coherency for the cached file data
99 across the cluster. This mount option works with Linux kernel
100 2.6.37 and later.
101 full This is the default mode. The file system ensures the
104 cached file data is coherent across the cluster for all
105 IO modes.
106 buffered
109 The file system only ensures the cached file data
110 coherency for buffered mode IOs. It does not perform IO
111 serialization for direct IOs. This allows multiple nodes
112 to perform concurrent direct IOs to the same file. This
113 is the recommended mode for volumes hosting database
114 files.
115 resv_level=level
118 Specifies the level of allocation reservation for files. The
119 higher the value, the more aggressive it is. Valid values are
120 between 0 (reservation off) to 8 (maximum space for reserva‐
121 tion). It defaults to 2. This mount option works with Linux ker‐
122 nel 2.6.35 and later.
123 dir_resv_level=level
126 By default, directory reservation scales with file reservera‐
127 tion. Users should rarely need to change this value. If the file
128 allocation reservation is turned off, this option will have no
129 effect. This mount option works with Linux kernel 2.6.35 and
130 later.
131 inode64
133 Indicates that the file system can create inodes at any location
134 in the volume, including those which will result in inode num‐
135 bers greater than 4 billion.
136 [no]intr
139 Specifies whether a signal can interrupt IOs. It is disabled by
140 default.
141 ro Mount the file system read-only.
144 rw Mount the file system read-write.
147
150 To mount and umount a OCFS2 volume, do:
151 # mount /dev/sda1 /mount/path
154 ...
155 # umount /mount/path
156 Users mounting a clustered volume should be aware of the following:
158 1. The cluster stack must to be online for a clustered mount to
160 succeed.
161 2. The clustered mount operation is not instantaneous; it must wait
163 for the node to join the DLM domain.
164 3. Likewise, clustered umount is also not instantaneous; it
166 involves migrating all mastered lock-resources to the other nodes
167 in the cluster.
168 If the mount fails, detailed errors can be found via dmesg(8). These
170 might include incorrect cluster configuration (say, a missing node or
171 incorrect IP address) or a firewall interfering with o2cb network traf‐
172 fic. Check the configuration as listed in o2cb(7) or the man page of
173 the active cluster stack.
174 To auto-mount volumes on startup, the file system tools include an
176 ocfs2 init service. This runs after the o2cb init service has started
177 the cluster. The ocfs2 init service mounts all OCFS2 volumes listed in
178 /etc/fstab.
179 # chkconfig --add o2cb
181 o2cb 0:off 1:off 2:on 3:on 4:off 5:on 6:off
182 $ chkconfig --add ocfs2
184 o2cb 0:off 1:off 2:on 3:on 4:off 5:on 6:off
185 $ cat /etc/fstab
187 ...
188 /dev/sda1 /u01 ocfs2 _netdev,defaults 0 0
189 ...
190
193 debugfs.ocfs2(8) fsck.ocfs2(8) mkfs.ocfs2(8) mounted.ocfs2(8) o2cb(7)
194 o2cluster(8) o2image(8) o2info(1) tunefs.ocfs2(8)
195
198 Oracle Corporation
199
202 Copyright © 2004, 2012 Oracle. All rights reserved.
203Version 1.8.6 January 2012 mount.ocfs2(8)