1mount.ocfs2(8)                OCFS2 Manual Pages                mount.ocfs2(8)
2
3
4

NAME

6       mount.ocfs2 -  mount an OCFS2 filesystem
7

SYNOPSIS

9       mount.ocfs2 [-vn] [-o options] device dir
10

DESCRIPTION

12       mount.ocfs2  mounts  an  OCFS2 filesystem at dir. It is usually invoked
13       indirectly by the mount(8) command.
14
15

OPTIONS

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  en‐
25              abled.
26
27
28       noatime
29              The file system will not update access time.
30
31
32       relatime
33              The  file  system will update atime only if the on-disk atime is
34              older than mtime or ctime. This is the default mode.
35
36
37       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 op‐
41              tions need work together.
42
43
44       [no]acl
45              Enables / disables POSIX ACLs (access control lists) support. It
46              is enabled by default.
47
48
49       [no]user_xattr
50              Enables / disables extended user attributes. It  is  enabled  by
51              default.
52
53
54       commit=nrsec
55              Sync  all  data  and  metadata  every nrsec seconds. The default
56              value is 5 seconds.  Zero means default.
57
58
59       data=[ordered|writeback]
60              Specifies the handling of file data during metadata journalling.
61
62
63              ordered
64                     This is the default mode. Data is flushed to disk  before
65                     the corresponding meta-data is committed to the journal.
66
67
68              writeback
69                     Data   ordering is not preserved - data may be flushed to
70                     disk after the corresponding meta-data  is  committed  to
71                     the  journal. This is rumored to be the higher-throughput
72                     option. While it guarantees internal file  system  integ‐
73                     rity,  it  can  allow old data to appear in files after a
74                     crash and journal recovery.
75
76
77       errors=[remount-ro|errors=panic|errors=continue]
78              Specifies the behavior when an  on-disk  corruption  is  encoun‐
79              tered.
80
81
82              remount-ro
83                     This  is  the  default mode. The file system is remounted
84                     read-only.
85
86
87              panic  The system is halted via panic.
88
89
90              continue
91                     Ignore errors. Just log error message, return error  code
92                     to the calling process and continue.
93
94
95       localflocks
96              This disables cluster-aware flock(2).
97
98
99       coherency=[full|coherency]
100              Specifies  the  extent  of  coherency  for  the cached file data
101              across the cluster.  This mount option works with  Linux  kernel
102              2.6.37 and later.
103
104
105              full   This  is  the  default  mode. The file system ensures the
106                     cached file data is coherent across the cluster  for  all
107                     IO modes.
108
109
110              buffered
111                     The  file  system  only  ensures the cached file data co‐
112                     herency for buffered mode IOs.  It does  not  perform  IO
113                     serialization  for direct IOs. This allows multiple nodes
114                     to perform concurrent direct IOs to the same  file.  This
115                     is  the  recommended  mode  for  volumes hosting database
116                     files.
117
118
119       resv_level=level
120              Specifies the level of allocation  reservation  for  files.  The
121              higher  the  value,  the more aggressive it is. Valid values are
122              between 0 (reservation off) to 8  (maximum  space  for  reserva‐
123              tion). It defaults to 2. This mount option works with Linux ker‐
124              nel 2.6.35 and later.
125
126
127       dir_resv_level=level
128              By default, directory reservation scales  with  file  reservera‐
129              tion. Users should rarely need to change this value. If the file
130              allocation reservation is turned off, this option will  have  no
131              effect.  This  mount  option  works with Linux kernel 2.6.35 and
132              later.
133
134       inode64
135              Indicates that the file system can create inodes at any location
136              in  the  volume, including those which will result in inode num‐
137              bers greater than 4 billion.
138
139
140       nocluster
141              This option allows users to mount  a  clustered  volume  without
142              configuring  the cluster stack.  However, you must be aware that
143              you can only mount the file system from one  node  at  the  same
144              time,  otherwise,  the file system may be damaged. Please use it
145              with caution.
146
147
148       [no]intr
149              Specifies whether a signal can interrupt IOs. It is disabled  by
150              default.
151
152
153       ro     Mount the file system read-only.
154
155
156       rw     Mount the file system read-write.
157
158

NOTES

160       To mount and umount a OCFS2 volume, do:
161
162
163       # mount /dev/sda1 /mount/path
164        ...
165       # umount /mount/path
166
167       Users mounting a clustered volume should be aware of the following:
168
169           1.  The  cluster  stack  must to be online for a clustered mount to
170           succeed.
171
172           2. The clustered mount operation is not instantaneous; it must wait
173           for the node to join the DLM domain.
174
175           3.  Likewise,  clustered  umount  is also not instantaneous; it in‐
176           volves migrating all mastered lock-resources to the other nodes  in
177           the cluster.
178
179       If  the  mount  fails, detailed errors can be found via dmesg(8). These
180       might include incorrect cluster configuration (say, a missing  node  or
181       incorrect IP address) or a firewall interfering with o2cb network traf‐
182       fic. Check the configuration as listed in o2cb(7) or the  man  page  of
183       the active cluster stack.
184
185       To  auto-mount  volumes  on  startup,  the file system tools include an
186       ocfs2 init service.  This runs after the o2cb init service has  started
187       the  cluster. The ocfs2 init service mounts all OCFS2 volumes listed in
188       /etc/fstab.
189
190       # chkconfig --add o2cb
191       o2cb 0:off 1:off 2:on 3:on 4:off 5:on 6:off
192
193       $ chkconfig --add ocfs2
194       o2cb 0:off 1:off 2:on 3:on 4:off 5:on 6:off
195
196       $ cat /etc/fstab
197        ...
198       /dev/sda1     /u01     ocfs2     _netdev,defaults     0  0
199        ...
200
201

SEE ALSO

203       debugfs.ocfs2(8) fsck.ocfs2(8) mkfs.ocfs2(8)  mounted.ocfs2(8)  o2cb(7)
204       o2cluster(8) o2image(8) o2info(1) tunefs.ocfs2(8)
205
206

AUTHORS

208       Oracle Corporation
209
210
212       Copyright © 2004, 2012 Oracle. All rights reserved.
213
214
215
216Version 1.8.7                    January 2012                   mount.ocfs2(8)
Impressum