[SCM] CTDB repository - branch master updated - ctdb-1.12-85-g6489d0d
Ronnie Sahlberg
sahlberg at samba.org
Tue Nov 29 16:43:13 MST 2011
The branch, master has been updated
via 6489d0d9b8ec14c7764a1865618faf659800bcc3 (commit)
via 36105b7283df729946e0a2ed61a696a14221efa6 (commit)
via c32604fd0016de0df14845a2f222edaa3c52a4fa (commit)
via e9250775f5a1234f27a1a62caa902d7b86194285 (commit)
via 92a391a81d0697956b96e96e39bb1b9d13e18097 (commit)
via ad64ef2c40a2a12b37dbf39142e95c6781c2fc3b (commit)
via 86d956170d4806065f1470fc44710c085c57f17a (commit)
via 502150c764298a9fa8c4d8aa445bf7d85d4ee9dc (commit)
via 6e96a62494bbb2c7b0682ebf0c2115dd2f44f7af (commit)
via 1fea9ef55a6a9d201ad1b49583451ac3e6b1c66d (commit)
from 3b6ef3442f0b62d65ec0f9be67a2b1dbf7e4af67 (commit)
http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 6489d0d9b8ec14c7764a1865618faf659800bcc3
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Wed Nov 30 10:05:59 2011 +1100
DOC: document the check_srvids debugging command
commit 36105b7283df729946e0a2ed61a696a14221efa6
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Wed Nov 30 10:00:27 2011 +1100
ctdb: use libctdb version of check-srvids call
commit c32604fd0016de0df14845a2f222edaa3c52a4fa
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Wed Nov 30 10:00:07 2011 +1100
LibCTDB: add support for the check-srvids control
commit e9250775f5a1234f27a1a62caa902d7b86194285
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Wed Nov 30 09:50:12 2011 +1100
check_srvids: remove the <pnn> from the commandline so that we only specify the list of <srvids>
Specifying the pnn can be done via '-n <pnn>'
commit 92a391a81d0697956b96e96e39bb1b9d13e18097
Author: Volker Lendecke <vl at samba.org>
Date: Mon Oct 31 16:21:54 2011 +0100
Add "ctdb check_srvid"
commit ad64ef2c40a2a12b37dbf39142e95c6781c2fc3b
Author: Volker Lendecke <vl at samba.org>
Date: Mon Oct 31 13:29:13 2011 +0100
Add CTDB_CONTROL_CHECK_SRVID
commit 86d956170d4806065f1470fc44710c085c57f17a
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Wed Nov 30 08:59:03 2011 +1100
DOC: describe the RecoverPDBBySeqNum tunable
commit 502150c764298a9fa8c4d8aa445bf7d85d4ee9dc
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Mon Nov 28 13:56:30 2011 +1100
Recover Persistent database DB by DB and not record by record
Add a new tunable that changes the mode how persistent databases are recovered.
RecoveryPDBBySeqNum
When set to 1, persistent databases will be recovered in whole from the node which
has the highest "__db_sequence_number__" record.
This record is managed by samba for those databases where we do persistent writes and have
inter-record relations.
For these databases we do not want the usual "blend records from all nodes based
on individual record RSN" but instead a mode where we pick one instance of the persistent database.
If no node was found with a "__db_sequence_number__" record at all, we fail back to the original "recover records independently based on record RSN".
Some persistent databases do not contain record interrelations and as such does not
contain this special record at all.
commit 6e96a62494bbb2c7b0682ebf0c2115dd2f44f7af
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Mon Nov 28 16:30:46 2011 +1100
LibCTDB: add get persistent db seqnum control
commit 1fea9ef55a6a9d201ad1b49583451ac3e6b1c66d
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Mon Nov 28 10:41:17 2011 +1100
DB Seqnum: must provide a ctdb_ltdb_header when calling ctdb_ltdb_fetch()
-----------------------------------------------------------------------
Summary of changes:
doc/ctdb.1 | 678 +++++++++++++++++-----------------------------
doc/ctdb.1.html | 166 ++++++------
doc/ctdb.1.xml | 19 ++
doc/ctdbd.1 | 593 ++++++++++++++++-------------------------
doc/ctdbd.1.html | 93 ++++---
doc/ctdbd.1.xml | 19 ++
include/ctdb.h | 121 ++++++++
include/ctdb_private.h | 3 +
include/ctdb_protocol.h | 1 +
libctdb/control.c | 84 ++++++
libctdb/sync.c | 36 +++
server/ctdb_control.c | 3 +
server/ctdb_daemon.c | 36 +++
server/ctdb_persistent.c | 3 +-
server/ctdb_recoverd.c | 126 +++++++++-
server/ctdb_tunables.c | 3 +-
tools/ctdb.c | 67 +++++
17 files changed, 1140 insertions(+), 911 deletions(-)
Changeset truncated at 500 lines:
diff --git a/doc/ctdb.1 b/doc/ctdb.1
index 4416f9f..70405d0 100644
--- a/doc/ctdb.1
+++ b/doc/ctdb.1
@@ -1,218 +1,164 @@
-'\" t
-.\" Title: ctdb
-.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
-.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
-.\" Date: 11/29/2011
-.\" Manual: CTDB - clustered TDB database
-.\" Source: ctdb
-.\" Language: English
-.\"
-.TH "CTDB" "1" "11/29/2011" "ctdb" "CTDB \- clustered TDB database"
-.\" -----------------------------------------------------------------
-.\" * Define some portability stuff
-.\" -----------------------------------------------------------------
-.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.\" http://bugs.debian.org/507673
-.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
-.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.ie \n(.g .ds Aq \(aq
-.el .ds Aq '
-.\" -----------------------------------------------------------------
-.\" * set default formatting
-.\" -----------------------------------------------------------------
+.\" ** You probably do not want to edit this file directly **
+.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
+.\" Instead of manually editing it, you probably should edit the DocBook XML
+.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
+.TH "CTDB" "1" "11/30/2011" "ctdb" "CTDB \- clustered TDB database"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
-.\" -----------------------------------------------------------------
-.\" * MAIN CONTENT STARTS HERE *
-.\" -----------------------------------------------------------------
.SH "NAME"
ctdb \- clustered tdb database management utility
.SH "SYNOPSIS"
-.HP \w'\fBctdb\ [\ OPTIONS\ ]\ COMMAND\ \&.\&.\&.\fR\ 'u
-\fBctdb [ OPTIONS ] COMMAND \&.\&.\&.\fR
-.HP \w'\fBctdb\fR\ 'u
+.HP 29
+\fBctdb [ OPTIONS ] COMMAND ...\fR
+.HP 5
\fBctdb\fR [\-n\ <node>] [\-Y] [\-t\ <timeout>] [\-T\ <timelimit>] [\-?\ \-\-help] [\-\-usage] [\-d\ \-\-debug=<INTEGER>] [\-\-socket=<filename>] [\-\-print\-emptyrecords] [\-\-print\-datasize] [\-\-print\-lmaster] [\-\-print\-hash] [\-\-print\-recordflags]
.SH "DESCRIPTION"
.PP
-ctdb is a utility to view and manage a ctdb cluster\&.
+ctdb is a utility to view and manage a ctdb cluster.
.SH "OPTIONS"
-.PP
+.TP
\-n <pnn>
-.RS 4
-This specifies the physical node number on which to execute the command\&. Default is to run the command on the daemon running on the local host\&.
+This specifies the physical node number on which to execute the command. Default is to run the command on the daemon running on the local host.
.sp
-The physical node number is an integer that describes the node in the cluster\&. The first node has physical node number 0\&.
-.RE
-.PP
+The physical node number is an integer that describes the node in the cluster. The first node has physical node number 0.
+.TP
\-Y
-.RS 4
-Produce output in machine readable form for easier parsing by scripts\&. Not all commands support this option\&.
-.RE
-.PP
+Produce output in machine readable form for easier parsing by scripts. Not all commands support this option.
+.TP
\-t <timeout>
-.RS 4
-How long should ctdb wait for the local ctdb daemon to respond to a command before timing out\&. Default is 3 seconds\&.
-.RE
-.PP
+How long should ctdb wait for the local ctdb daemon to respond to a command before timing out. Default is 3 seconds.
+.TP
\-T <timelimit>
-.RS 4
-A limit on how long the ctdb command will run for before it will be aborted\&. When this timelimit has been exceeded the ctdb command will terminate\&.
-.RE
-.PP
+A limit on how long the ctdb command will run for before it will be aborted. When this timelimit has been exceeded the ctdb command will terminate.
+.TP
\-? \-\-help
-.RS 4
-Print some help text to the screen\&.
-.RE
-.PP
+Print some help text to the screen.
+.TP
\-\-usage
-.RS 4
-Print useage information to the screen\&.
-.RE
-.PP
+Print useage information to the screen.
+.TP
\-d \-\-debug=<debuglevel>
-.RS 4
-Change the debug level for the command\&. Default is 0\&.
-.RE
-.PP
+Change the debug level for the command. Default is 0.
+.TP
\-\-socket=<filename>
-.RS 4
-Specify the socketname to use when connecting to the local ctdb daemon\&. The default is /tmp/ctdb\&.socket \&.
+Specify the socketname to use when connecting to the local ctdb daemon. The default is /tmp/ctdb.socket .
.sp
-You only need to specify this parameter if you run multiple ctdb daemons on the same physical host and thus can not use the default name for the domain socket\&.
-.RE
-.PP
+You only need to specify this parameter if you run multiple ctdb daemons on the same physical host and thus can not use the default name for the domain socket.
+.TP
\-\-print\-emptyrecords
-.RS 4
-This enables printing of empty records when dumping databases with the catdb, cattbd and dumpdbbackup commands\&. Records with empty data segment are considered deleted by ctdb and cleaned by the vacuuming mechanism, so this switch can come in handy for debugging the vacuuming behaviour\&.
-.RE
-.PP
+This enables printing of empty records when dumping databases with the catdb, cattbd and dumpdbbackup commands. Records with empty data segment are considered deleted by ctdb and cleaned by the vacuuming mechanism, so this switch can come in handy for debugging the vacuuming behaviour.
+.TP
\-\-print\-datasize
-.RS 4
-This lets database dumps (catdb, cattdb, dumpdbbackup) print the size of the record data instead of dumping the data contents\&.
-.RE
-.PP
+This lets database dumps (catdb, cattdb, dumpdbbackup) print the size of the record data instead of dumping the data contents.
+.TP
\-\-print\-lmaster
-.RS 4
-This lets catdb print the lmaster for each record\&.
-.RE
-.PP
+This lets catdb print the lmaster for each record.
+.TP
\-\-print\-hash
-.RS 4
-This lets database dumps (catdb, cattdb, dumpdbbackup) print the hash for each record\&.
-.RE
-.PP
+This lets database dumps (catdb, cattdb, dumpdbbackup) print the hash for each record.
+.TP
\-\-print\-recordflags
-.RS 4
-This lets catdb and dumpdbbackup print the record flags for each record\&. Note that cattdb always prints the flags\&.
-.RE
+This lets catdb and dumpdbbackup print the record flags for each record. Note that cattdb always prints the flags.
.SH "ADMINISTRATIVE COMMANDS"
.PP
-These are commands used to monitor and administrate a CTDB cluster\&.
+These are commands used to monitor and administrate a CTDB cluster.
.SS "pnn"
.PP
-This command displays the pnn of the current node\&.
+This command displays the pnn of the current node.
.SS "status"
.PP
-This command shows the current status of the ctdb node\&.
+This command shows the current status of the ctdb node.
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-.ps +1
\fBnode status\fR
-.RS 4
+.RS 3
.PP
-Node status reflects the current status of the node\&. There are five possible states:
+Node status reflects the current status of the node. There are five possible states:
.PP
-OK \- This node is fully functional\&.
+OK \- This node is fully functional.
.PP
-DISCONNECTED \- This node could not be connected through the network and is currently not participating in the cluster\&. If there is a public IP address associated with this node it should have been taken over by a different node\&. No services are running on this node\&.
+DISCONNECTED \- This node could not be connected through the network and is currently not participating in the cluster. If there is a public IP address associated with this node it should have been taken over by a different node. No services are running on this node.
.PP
-DISABLED \- This node has been administratively disabled\&. This node is still functional and participates in the CTDB cluster but its IP addresses have been taken over by a different node and no services are currently being hosted\&.
+DISABLED \- This node has been administratively disabled. This node is still functional and participates in the CTDB cluster but its IP addresses have been taken over by a different node and no services are currently being hosted.
.PP
-UNHEALTHY \- A service provided by this node is malfunctioning and should be investigated\&. The CTDB daemon itself is operational and participates in the cluster\&. Its public IP address has been taken over by a different node and no services are currnetly being hosted\&. All unhealthy nodes should be investigated and require an administrative action to rectify\&.
+UNHEALTHY \- A service provided by this node is malfunctioning and should be investigated. The CTDB daemon itself is operational and participates in the cluster. Its public IP address has been taken over by a different node and no services are currnetly being hosted. All unhealthy nodes should be investigated and require an administrative action to rectify.
.PP
-BANNED \- This node failed too many recovery attempts and has been banned from participating in the cluster for a period of RecoveryBanPeriod seconds\&. Any public IP address has been taken over by other nodes\&. This node does not provide any services\&. All banned nodes should be investigated and require an administrative action to rectify\&. This node does not perticipate in the CTDB cluster but can still be communicated with\&. I\&.e\&. ctdb commands can be sent to it\&.
+BANNED \- This node failed too many recovery attempts and has been banned from participating in the cluster for a period of RecoveryBanPeriod seconds. Any public IP address has been taken over by other nodes. This node does not provide any services. All banned nodes should be investigated and require an administrative action to rectify. This node does not perticipate in the CTDB cluster but can still be communicated with. I.e. ctdb commands can be sent to it.
.PP
-STOPPED \- A node that is stopped does not host any public ip addresses, nor is it part of the VNNMAP\&. A stopped node can not become LVSMASTER, RECMASTER or NATGW\&. This node does not perticipate in the CTDB cluster but can still be communicated with\&. I\&.e\&. ctdb commands can be sent to it\&.
+STOPPED \- A node that is stopped does not host any public ip addresses, nor is it part of the VNNMAP. A stopped node can not become LVSMASTER, RECMASTER or NATGW. This node does not perticipate in the CTDB cluster but can still be communicated with. I.e. ctdb commands can be sent to it.
.PP
-PARTIALLYONLINE \- A node that is partially online participates in a cluster like a node that is ok\&. Some interfaces to serve public ip addresses are down, but at least one interface is up\&. See also "ctdb ifaces"\&.
+PARTIALLYONLINE \- A node that is partially online participates in a cluster like a node that is ok. Some interfaces to serve public ip addresses are down, but at least one interface is up. See also "ctdb ifaces".
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-.ps +1
\fBgeneration\fR
-.RS 4
+.RS 3
.PP
-The generation id is a number that indicates the current generation of a cluster instance\&. Each time a cluster goes through a reconfiguration or a recovery its generation id will be changed\&.
+The generation id is a number that indicates the current generation of a cluster instance. Each time a cluster goes through a reconfiguration or a recovery its generation id will be changed.
.PP
-This number does not have any particular meaning other than to keep track of when a cluster has gone through a recovery\&. It is a random number that represents the current instance of a ctdb cluster and its databases\&. CTDBD uses this number internally to be able to tell when commands to operate on the cluster and the databases was issued in a different generation of the cluster, to ensure that commands that operate on the databases will not survive across a cluster database recovery\&. After a recovery, all old outstanding commands will automatically become invalid\&.
+This number does not have any particular meaning other than to keep track of when a cluster has gone through a recovery. It is a random number that represents the current instance of a ctdb cluster and its databases. CTDBD uses this number internally to be able to tell when commands to operate on the cluster and the databases was issued in a different generation of the cluster, to ensure that commands that operate on the databases will not survive across a cluster database recovery. After a recovery, all old outstanding commands will automatically become invalid.
.PP
-Sometimes this number will be shown as "INVALID"\&. This only means that the ctdbd daemon has started but it has not yet merged with the cluster through a recovery\&. All nodes start with generation "INVALID" and are not assigned a real generation id until they have successfully been merged with a cluster through a recovery\&.
+Sometimes this number will be shown as "INVALID". This only means that the ctdbd daemon has started but it has not yet merged with the cluster through a recovery. All nodes start with generation "INVALID" and are not assigned a real generation id until they have successfully been merged with a cluster through a recovery.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-.ps +1
\fBVNNMAP\fR
-.RS 4
+.RS 3
.PP
-The list of Virtual Node Numbers\&. This is a list of all nodes that actively participates in the cluster and that share the workload of hosting the Clustered TDB database records\&. Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record\&.
+The list of Virtual Node Numbers. This is a list of all nodes that actively participates in the cluster and that share the workload of hosting the Clustered TDB database records. Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-.ps +1
\fBRecovery mode\fR
-.RS 4
+.RS 3
.PP
-This is the current recovery mode of the cluster\&. There are two possible modes:
+This is the current recovery mode of the cluster. There are two possible modes:
.PP
-NORMAL \- The cluster is fully operational\&.
+NORMAL \- The cluster is fully operational.
.PP
-RECOVERY \- The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete\&. A recovery process should finish within seconds\&. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated\&.
+RECOVERY \- The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete. A recovery process should finish within seconds. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated.
.PP
-Once the recovery master detects an inconsistency, for example a node becomes disconnected/connected, the recovery daemon will trigger a cluster recovery process, where all databases are remerged across the cluster\&. When this process starts, the recovery master will first "freeze" all databases to prevent applications such as samba from accessing the databases and it will also mark the recovery mode as RECOVERY\&.
+Once the recovery master detects an inconsistency, for example a node becomes disconnected/connected, the recovery daemon will trigger a cluster recovery process, where all databases are remerged across the cluster. When this process starts, the recovery master will first "freeze" all databases to prevent applications such as samba from accessing the databases and it will also mark the recovery mode as RECOVERY.
.PP
-When CTDBD starts up, it will start in RECOVERY mode\&. Once the node has been merged into a cluster and all databases have been recovered, the node mode will change into NORMAL mode and the databases will be "thawed", allowing samba to access the databases again\&.
+When CTDBD starts up, it will start in RECOVERY mode. Once the node has been merged into a cluster and all databases have been recovered, the node mode will change into NORMAL mode and the databases will be "thawed", allowing samba to access the databases again.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-.ps +1
\fBRecovery master\fR
-.RS 4
+.RS 3
.PP
-This is the cluster node that is currently designated as the recovery master\&. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired\&.
+This is the cluster node that is currently designated as the recovery master. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired.
.PP
-Only one node at a time can be the designated recovery master\&. Which node is designated the recovery master is decided by an election process in the recovery daemons running on each node\&.
+Only one node at a time can be the designated recovery master. Which node is designated the recovery master is decided by an election process in the recovery daemons running on each node.
.RE
.PP
Example: ctdb status
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
Number of nodes:4
-pnn:0 11\&.1\&.2\&.200 OK (THIS NODE)
-pnn:1 11\&.1\&.2\&.201 OK
-pnn:2 11\&.1\&.2\&.202 OK
-pnn:3 11\&.1\&.2\&.203 OK
+pnn:0 11.1.2.200 OK (THIS NODE)
+pnn:1 11.1.2.201 OK
+pnn:2 11.1.2.202 OK
+pnn:3 11.1.2.203 OK
Generation:1362079228
Size:4
hash:0 lmaster:0
@@ -223,86 +169,62 @@ Recovery mode:NORMAL (0)
Recovery master:0
.fi
-.if n \{\
-.RE
-.\}
.SS "recmaster"
.PP
-This command shows the pnn of the node which is currently the recmaster\&.
+This command shows the pnn of the node which is currently the recmaster.
.SS "uptime"
.PP
-This command shows the uptime for the ctdb daemon\&. When the last recovery or ip\-failover completed and how long it took\&. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago\&.
+This command shows the uptime for the ctdb daemon. When the last recovery or ip\-failover completed and how long it took. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago.
.PP
Example: ctdb uptime
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
Current time of node : Thu Oct 29 10:38:54 2009
Ctdbd start time : (000 16:54:28) Wed Oct 28 17:44:26 2009
Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
-Duration of last recovery/failover: 2\&.248552 seconds
+Duration of last recovery/failover: 2.248552 seconds
.fi
-.if n \{\
-.RE
-.\}
.SS "listnodes"
.PP
-This command shows lists the ip addresses of all the nodes in the cluster\&.
+This command shows lists the ip addresses of all the nodes in the cluster.
.PP
Example: ctdb listnodes
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
-10\&.0\&.0\&.71
-10\&.0\&.0\&.72
-10\&.0\&.0\&.73
-10\&.0\&.0\&.74
+10.0.0.71
+10.0.0.72
+10.0.0.73
+10.0.0.74
.fi
-.if n \{\
-.RE
-.\}
.SS "ping"
.PP
-This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly\&.
+This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly.
.PP
Example: ctdb ping
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
-response from 0 time=0\&.000054 sec (3 clients)
-response from 1 time=0\&.000144 sec (2 clients)
-response from 2 time=0\&.000105 sec (2 clients)
-response from 3 time=0\&.000114 sec (2 clients)
+response from 0 time=0.000054 sec (3 clients)
+response from 1 time=0.000144 sec (2 clients)
+response from 2 time=0.000105 sec (2 clients)
+response from 3 time=0.000114 sec (2 clients)
.fi
-.if n \{\
-.RE
-.\}
.SS "ifaces"
.PP
-This command will display the list of network interfaces, which could host public addresses, along with their status\&.
+This command will display the list of network interfaces, which could host public addresses, along with their status.
.PP
Example: ctdb ifaces
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
Interfaces on node 0
name:eth5 link:up references:2
@@ -311,17 +233,11 @@ name:eth3 link:up references:1
name:eth2 link:up references:1
.fi
-.if n \{\
-.RE
-.\}
.PP
Example: ctdb ifaces \-Y
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
:Name:LinkStatus:References:
:eth5:1:2
@@ -330,157 +246,121 @@ Example output:
:eth2:1:1
.fi
-.if n \{\
-.RE
-.\}
.SS "setifacelink <iface> <status>"
.PP
-This command will set the status of a network interface\&. The status needs to be "up" or "down"\&. This is typically used in the 10\&.interfaces script in the "monitor" event\&.
+This command will set the status of a network interface. The status needs to be "up" or "down". This is typically used in the 10.interfaces script in the "monitor" event.
.PP
Example: ctdb setifacelink eth0 up
.SS "ip"
.PP
-This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip\&. By default this command will ONLY show those public addresses that are known to the node itself\&. To see the full list of all public ips across the cluster you must use "ctdb ip \-n all"\&.
+This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip. By default this command will ONLY show those public addresses that are known to the node itself. To see the full list of all public ips across the cluster you must use "ctdb ip \-n all".
.PP
Example: ctdb ip
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
Public IPs on node 0
-172\&.31\&.91\&.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.91\&.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.91\&.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.91\&.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.92\&.82 node[1] active[] available[eth5] configured[eth4,eth5]
-172\&.31\&.92\&.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
-172\&.31\&.92\&.84 node[1] active[] available[eth5] configured[eth4,eth5]
-172\&.31\&.92\&.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
+172.31.91.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
+172.31.91.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
+172.31.91.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
+172.31.91.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
+172.31.92.82 node[1] active[] available[eth5] configured[eth4,eth5]
+172.31.92.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
+172.31.92.84 node[1] active[] available[eth5] configured[eth4,eth5]
+172.31.92.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
.fi
-.if n \{\
-.RE
-.\}
.PP
Example: ctdb ip \-Y
.PP
Example output:
.sp
-.if n \{\
-.RS 4
-.\}
.nf
:Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces:
-:172\&.31\&.91\&.82:1::eth2,eth3:eth2,eth3:
-:172\&.31\&.91\&.83:0:eth3:eth2,eth3:eth2,eth3:
-:172\&.31\&.91\&.84:1::eth2,eth3:eth2,eth3:
-:172\&.31\&.91\&.85:0:eth2:eth2,eth3:eth2,eth3:
-:172\&.31\&.92\&.82:1::eth5:eth4,eth5:
-:172\&.31\&.92\&.83:0:eth5:eth5:eth4,eth5:
-:172\&.31\&.92\&.84:1::eth5:eth4,eth5:
-:172\&.31\&.92\&.85:0:eth5:eth5:eth4,eth5:
+:172.31.91.82:1::eth2,eth3:eth2,eth3:
+:172.31.91.83:0:eth3:eth2,eth3:eth2,eth3:
+:172.31.91.84:1::eth2,eth3:eth2,eth3:
+:172.31.91.85:0:eth2:eth2,eth3:eth2,eth3:
+:172.31.92.82:1::eth5:eth4,eth5:
+:172.31.92.83:0:eth5:eth5:eth4,eth5:
+:172.31.92.84:1::eth5:eth4,eth5:
+:172.31.92.85:0:eth5:eth5:eth4,eth5:
.fi
-.if n \{\
-.RE
-.\}
.SS "ipinfo <ip>"
.PP
-This command will display details about the specified public addresses\&.
+This command will display details about the specified public addresses.
.PP
-Example: ctdb ipinfo 172\&.31\&.92\&.85
+Example: ctdb ipinfo 172.31.92.85
.PP
Example output:
.sp
-.if n \{\
--
CTDB repository
More information about the samba-cvs
mailing list