1o2cluster(8) OCFS2 Manual Pages o2cluster(8)
2
6 o2cluster - Change cluster stack stamped on an OCFS2 file system.
7
9 o2cluster [-o|--show-ondisk] [-r|--show-running] [-u|--update[=<clus‐
10 terstack>]] [-hvVyn] [device]
11
14 o2cluster is used to change the cluster stack stamped on an OCFS2 file
15 system. It also used to list the active cluster stack and the one
16 stamped on-disk. This utility does not expect the cluster to be online.
17 It only updates the file system if it is reasonably assured that it is
18 not in-use on any other node. Clean journals implies the file system is
19 not in-use. This utility aborts if it detects even one dirty journal.
20 Before using this utility, the user should use other means to ensure
22 that the volume is not in-use, and more importantly, not about to be
23 put in-use. While clean journals implies the file system is not in-use,
24 there is a tiny window after the check and before the update during
25 which another node could mount the file system using the older cluster
26 stack.
27 If a dirty journal is detected, it implies one of two scenarios. Either
29 the file system is mounted on another node, or, the last node to have
30 it mounted, crashed. There is no way, short of joining the cluster,
31 that the utility can use to differentiate between the two. Considering
32 this utility is targeted to be used in scenarios when the user is look‐
33 ing to change the on-disk cluster stack, it becomes a chicken-and-egg
34 problem.
35 If one were to run into this scenario, the user should manually re-con‐
37 firm that the file system is not in-use on another node and then run
38 fsck.ocfs2(8). It will update the on-disk cluster stack to the active
39 cluster stack, and, do a complete file system check.
40
43 The cluster stack can be specified in one of two forms. The first as
44 default, denoting the original classic o2cb cluster stack with local
45 heartbeat. The second as a triplet with the stack name, the cluster
46 name and the cluster flags separated by commas. Like o2cb,myclus‐
47 ter,global.
48 The valid stack names are o2cb, pcmk, and cman.
50 The cluster name can be up to 16 characters. The o2cb stack further re‐
52 stricts the names to contain only alphanumeric characters.
53 The valid flags for the o2cb stack are local and global, denoting the
55 two heartbeat modes. The only valid flag for the other stacks is none.
56
59 -o|--show-ondisk
60 Shows the cluster stack stamped on-disk.
61 -r|--show-running
64 Shows the active cluster stack.
65 -u|--update[=<clusterstack>]
68 Updates the on-disk cluster stack with the one provided. If no
69 cluster stack is provided, the utility detects the active clus‐
70 ter stack and stamps it on-disk.
71 -v, --verbose
74 Verbose mode.
75 -V, --version
78 Show version and exit.
79 -y, --yes
82 Always answer Yes in interactive command line.
83 -n, --no
86 Always answer No in interactive command line.
87
90 # o2cluster -r
91 o2cb,myactivecluster,global
92 # o2cluster -o /dev/sda1
94 o2cb,mycluster,global
95 # o2cluster --update=o2cb,yourcluster,global /dev/sdb1
97 Changing the clusterstack from o2cb,mycluster,global to o2cb,yourcluster,global. Continue? y
98 Updated successfully.
99
103 debugfs.ocfs2(8) fsck.ocfs2(8) fsck.ocfs2.checks(8) mkfs.ocfs2(8)
104 mount.ocfs2(8) mounted.ocfs2(8) o2image(8) o2info(1) tunefs.ocfs2(8)
105
108 Oracle Corporation
109
112 Copyright © 2011, 2012 Oracle. All rights reserved.
113Version 1.8.7 January 2012 o2cluster(8)