From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 1/2] pvecm: node revomal: rephrase warning about number of nodes
Date: Fri, 6 Feb 2026 16:23:49 +0100 [thread overview]
Message-ID: <20260206152350.1261246-1-a.lauterer@proxmox.com> (raw)
this way it is more readable and the important thing to look out for is
mentioned in the beginning.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvecm.adoc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 0ed1bd2..6d15e99 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -343,12 +343,12 @@ node automatically.
of any OSD, especially the last one on a node, will trigger a data
rebalance in Ceph.
-NOTE: By default, Ceph pools have a `size/min_size` of `3/2` and a
-full node as `failure domain` at the object balancer
-xref:pve_ceph_device_classes[CRUSH]. So if less than `size` (`3`)
-nodes with running OSDs are online, data redundancy will be degraded.
-If less than `min_size` are online, pool I/O will be blocked and
-affected guests may crash.
+NOTE: Make sure that there are still enough nodes with OSDs available to satisfy
+the `size/min_size` parameters configured for the Ceph pools. If there are fewer
+than `size` (default: 3) nodes available, data redundancy will be degraded. If
+there are fewer than `min_size` (default: 2) nodes available, the I/O of the
+pools will be blocked until there are enough replicas available. Affected guests
+may crash if their I/O is blocked.
* Ensure that sufficient xref:pve_ceph_monitors[monitors],
xref:pve_ceph_manager[managers] and, if using CephFS,
--
2.47.3
next reply other threads:[~2026-02-06 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 15:23 Aaron Lauterer [this message]
2026-02-06 15:23 ` [PATCH docs 2/2] pvecm: node removal: indent notes on prerequisites Aaron Lauterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260206152350.1261246-1-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox