X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pmxcfs.adoc;h=764cdf452470f91185e0618aa0256adcb645c11a;hp=0a07f39ca6d32a93e381398cb06391c3fa81a968;hb=119de2983578907f096315aee4da1677e89b6ad5;hpb=5f09af76d7282a043be8fa5439349272f506cf02 diff --git a/pmxcfs.adoc b/pmxcfs.adoc index 0a07f39..764cdf4 100644 --- a/pmxcfs.adoc +++ b/pmxcfs.adoc @@ -1,8 +1,7 @@ ifdef::manvolnum[] -PVE({manvolnum}) -================ +pmxcfs(8) +========= include::attributes.txt[] - :pve-toplevel: NAME @@ -13,7 +12,7 @@ pmxcfs - Proxmox Cluster File System SYNOPSIS -------- -include::pmxcfs.8-cli.adoc[] +include::pmxcfs.8-synopsis.adoc[] DESCRIPTION ----------- @@ -23,11 +22,8 @@ ifndef::manvolnum[] Proxmox Cluster File System (pmxcfs) ==================================== include::attributes.txt[] -endif::manvolnum[] - -ifdef::wiki[] :pve-toplevel: -endif::wiki[] +endif::manvolnum[] The Proxmox Cluster file system (``pmxcfs'') is a database-driven file system for storing configuration files, replicated in real time to all @@ -178,34 +174,9 @@ The recommended way is to reinstall the node after you removed it from your cluster. This makes sure that all secret cluster/ssh keys and any shared configuration data is destroyed. -In some cases, you might prefer to put a node back to local mode -without reinstall, which is described here: - -* stop the cluster file system in `/etc/pve/` - - # systemctl stop pve-cluster - -* start it again but forcing local mode - - # pmxcfs -l - -* remove the cluster configuration - - # rm /etc/pve/cluster.conf - # rm /etc/cluster/cluster.conf - # rm /var/lib/pve-cluster/corosync.authkey - -* stop the cluster file system again - - # systemctl stop pve-cluster - -* restart PVE services (or reboot) - - # systemctl start pve-cluster - # systemctl restart pvedaemon - # systemctl restart pveproxy - # systemctl restart pvestatd - +In some cases, you might prefer to put a node back to local mode without +reinstall, which is described in +<> ifdef::manvolnum[] include::pve-copyright.adoc[]