proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-08-06 22:10:50 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix typos in pvecm.adoc

Browse Source 
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fabian Ebner 2019-09-02 11:19:56 +02:00 committed by Thomas Lamprecht
parent 620d6725f0
commit 6d3c0b3479
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pvecm.adoc
View File

@ -40,7 +40,7 @@ Grouping nodes into a cluster has the following advantages:
* Centralized, web based management * Centralized, web based management
* Multi-master clusters: each node can do all management task * Multi-master clusters: each node can do all management tasks
* `pmxcfs`: database-driven file system for storing configuration files, * `pmxcfs`: database-driven file system for storing configuration files,
replicated in real-time on all nodes using `corosync`. replicated in real-time on all nodes using `corosync`.
@ -1084,7 +1084,7 @@ pvecm expected 1
This sets the expected vote count to 1 and makes the cluster quorate. You can This sets the expected vote count to 1 and makes the cluster quorate. You can
now fix your configuration, or revert it back to the last working backup. now fix your configuration, or revert it back to the last working backup.
This is not enough if corosync cannot start anymore. Here its best to edit the This is not enough if corosync cannot start anymore. Here it is best to edit the
local copy of the corosync configuration in '/etc/corosync/corosync.conf' so local copy of the corosync configuration in '/etc/corosync/corosync.conf' so
that corosync can start again. Ensure that on all nodes this configuration has that corosync can start again. Ensure that on all nodes this configuration has
the same content to avoid split brains. If you are not sure what went wrong the same content to avoid split brains. If you are not sure what went wrong
@ -1149,7 +1149,7 @@ example passwords or encryption keys).
Therefore, we strongly recommend using the secure channel if you do Therefore, we strongly recommend using the secure channel if you do
not have full control over the network and can not guarantee that no not have full control over the network and can not guarantee that no
one is eavesdropping to it. one is eavesdropping on it.
NOTE: Storage migration does not follow this setting. Currently, it NOTE: Storage migration does not follow this setting. Currently, it
always sends the storage content over a secure channel. always sends the storage content over a secure channel.