From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs 1/1] ceph: add warning about mixing device-specific with device-unspecific CRUSH rules when using autoscaler
Date: Tue, 21 Apr 2026 10:05:33 +0200 [thread overview]
Message-ID: <20260421080533.105169-1-n.frey@proxmox.com> (raw)
Suggested-by: Friedrich Weber <f.weber@proxmox.com>
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
pveceph.adoc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/pveceph.adoc b/pveceph.adoc
index 2aae6d6..dfa5d95 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -916,6 +916,9 @@ TIP: If the pool already contains objects, these must be moved accordingly.
Depending on your setup, this may introduce a big performance impact on your
cluster. As an alternative, you can create a new pool and move disks separately.
+WARNING: When using the autoscaler, all pools must either exclusively be assigned
+device-specific or device-unspecific CRUSH rules. Mixing them across pools will
+prevent the autoscaler from functioning.
Ceph Client
-----------
--
2.47.3
reply other threads:[~2026-04-21 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260421080533.105169-1-n.frey@proxmox.com \
--to=n.frey@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