From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/2] pvecm: node removal: indent notes on prerequisites
Date: Fri, 6 Feb 2026 16:23:50 +0100 [thread overview]
Message-ID: <20260206152350.1261246-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20260206152350.1261246-1-a.lauterer@proxmox.com>
this way it is clearer that the notes are part of the list item
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
I consider this patch optional, but from a readability POV I kinda prefer the
indented notes
pvecm.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 6d15e99..0636b12 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -330,7 +330,7 @@ Prerequisites
* Back up all local data on the node to be deleted.
* Make sure the node to be deleted is not part of any replication job
anymore.
-
++
CAUTION: If you fail to remove replication jobs from a node before
removing the node itself, the replication job will become irremovable.
Note that replication automatically switches direction when a
@@ -342,7 +342,7 @@ node automatically.
and that the OSDs are running (i.e. `up` and `in`). The destruction
of any OSD, especially the last one on a node, will trigger a data
rebalance in Ceph.
-
++
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
--
2.47.3
prev parent 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 [PATCH docs 1/2] pvecm: node revomal: rephrase warning about number of nodes Aaron Lauterer
2026-02-06 15:23 ` Aaron Lauterer [this message]
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-2-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