o2cb_ctl(8) [debian man page]
o2cb_ctl(8) OCFS2 Manual Pages o2cb_ctl(8) NAME
o2cb_ctl - Control program for the O2CB cluster service. SYNOPSIS
o2cb_ctl -C -n object -t type [-i] [-a attribute ] o2cb_ctl -D -n object [-u] o2cb_ctl -I [-o-z] -l manager> [-n object>] [-t type] [-a attribute] o2cb_ctl -H [-n object] [-t type>] [-a attribute>] o2cb_ctl -h o2cb_ctl -V DESCRIPTION
o2cb_ctl is the control program for the O2CB cluster service. Users are not advised to use this program directly but instead use the O2CB init service and/or ocfs2console. OPTIONS
-C Create an object in the OCFS2 Cluster Configuration. -D Delete an object from the existing OCFS2 Cluster Configuration. -I Print information about the OCFS2 Cluster Configuration. -H Change an object or objects in the existing OCFS2 Cluster Configuration. -h Displays help and exit. -V Print version and exit. OTHER OPTIONS
-a <attribute> With -C, <attribute> is in format "parameter=value", where the parameter is a valid parameter that can be set in the file /etc/ocfs2/cluster.conf. With -I, <attribute> may be "parameter", indicating an attribute to be listed in the output, or it may be "parameter==value", indicating that only objects matching "parameter=value" are to be displayed. -i Valid only with -C. When creating something (node or cluster), it will also install it in the live cluster. If the parameter is not specified, then only update the /etc/ocfs2/cluster.conf. -n object object is usually the node name or cluster name. In the /etc/ocfs2/cluster.conf file, it would be the value of the name parameter for any of the sections (cluster or node). -o Valid only with -I. Using this parameter, if one asks o2cb_ctl to list all nodes, it will output it in a format suitable for shell parsing. -t type type can be cluster, node or heartbeat. -u Valid only with -D. When deleting something (node or cluster), it will also remove it from the live cluster. If the parameter is not specified, then only update the /etc/ocfs2/cluster.conf. -z Valid only with -I. This is the default. If one asks o2cb_ctl to list all nodes, it will give a verbose listing. EXAMPLES
Add node5 to an offline cluster: $ o2cb_ctl -C -n node5 -t node -a number=5 -a ip_address=192.168.0.5 -a ip_port=7777 -a cluster=mycluster Add node10 to an online cluster: $ o2cb_ctl -C -i -n node10 -t node -a number=10 -a ip_address=192.168.1.10 -a ip_port=7777 -a cluster=mycluster Note the -i argument. Query the IP address of node5: $ o2cb_ctl -I -n node5 -a ip_address Change the IP address of node5: $ o2cb_ctl -H -n node5 -a ip_address=192.168.1.5 SEE ALSO
mkfs.ocfs2(8) fsck.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8) ocfs2console(8) o2cb(7) AUTHORS
Oracle Corporation COPYRIGHT
Copyright (C) 2004, 2010 Oracle. All rights reserved. Version 1.6.4 September 2010 o2cb_ctl(8)
Check Out this Related Man Page
fsck.ocfs2(8) OCFS2 Manual Pages fsck.ocfs2(8) NAME
fsck.ocfs2 - Check an OCFS2 file system. SYNOPSIS
fsck.ocfs2 [ -pafFGnuvVy ] [ -b superblock block ] [ -B block size ] device DESCRIPTION
fsck.ocfs2 is used to check an OCFS2 file system. device is the file where the file system is stored (e.g. /dev/sda1). It will almost always be a device file but a regular file will work as well. OPTIONS
-a This option does the same thing as the -p option. It is provided for backwards compatibility only: it is suggested that people use the -p option whenever possible. -b superblock block Normally, fsck.ocfs2 will read the superblock from the first block of the device. This option specifies an alternate block that the superblock should be read from. (Use -r instead of this option.) -B blocksize The block size, specified in bytes, can range from 512 to 4096. A value of 0, the default, is used to indicate that the blocksize should be automatically detected. -D Optimize directories in filesystem. This option causes fsck.ocfs2 to coalesce the directory entries in order to improve the filesys- tem performance. -f Force checking even if the file system is clean. -F By default fsck.ocfs2 will check with the cluster services to ensure that the volume is not in-use (mounted) on any node in the cluster before proceeding. -F skips this check and should only be used when it can be guaranteed that the volume is not mounted on any node in the cluster. WARNING: If the cluster check is disabled and the volume is mounted on one or more nodes, file system cor- ruption is very likely. If unsure, do not use this option. -G Usually fsck.ocfs2 will silently assume inodes whose generation number does not match the generation number of the super block are unused inodes. This option causes fsck.ocfs2 to ask the user if these inodes should in fact be marked unused. -n Give the 'no' answer to all questions that fsck will ask. This guarantees that the file system will not be modified and the device will be opened read-only. The output of fsck.ocfs2 with this option can be redirected to produce a record of a file system's faults. -p Automatically repair ("preen") the file system. This option will cause fsck.ocfs2 to automatically fix any problem that can be safely corrected without human intervention. If there are problems that require intervention, the descriptions will be printed and fsck.ocfs2 will exit with the value 4 logically or'd into the exit code. (See the EXIT CODE section.) This option is normally used by the system's boot scripts. -r backup-number mkfs.ocfs2 makes upto 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of the vol- ume. Use this option to specify the backup, 1 thru 6, to use to recover the superblock. -y Give the 'yes' answer to all questions that fsck will ask. This will repair all faults that fsck.ocfs2 finds but will not give the operator a chance to intervene if fsck.ocfs2 decides that it wants to drastically repair the file system. -v This option causes fsck.ocfs2 to produce a very large amount of debugging output. -V Print version information and exit. EXIT CODE
The exit code returned by fsck.ocfs2 is the sum of the following conditions: 0 - No errors 1 - File system errors corrected 2 - File system errors corrected, system should be rebooted 4 - File system errors left uncorrected 8 - Operational error 16 - Usage or syntax error 32 - fsck.ocfs2 canceled by user request 128 - Shared library error SEE ALSO
mkfs.ocfs2(8) debugfs.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8) ocfs2console(8) o2cb(7) AUTHORS
Oracle Corporation. This man page entry derives some text, especially the exit code summary, from e2fsck(8) by Theodore Y. Ts'o <tytso@mit.edu>. COPYRIGHT
Copyright (C) 2004, 2010 Oracle. All rights reserved. Version 1.6.4 September 2010 fsck.ocfs2(8)