From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation
Date: Tue, 3 May 2022 13:58:09 +0200 [thread overview]
Message-ID: <20220503115809.2566406-4-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20220503115809.2566406-1-a.lauterer@proxmox.com>
Some optional parameters will only be used for the replicated metadata
pool.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pveceph.adoc | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/pveceph.adoc b/pveceph.adoc
index dff44e0..abc749b 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -595,6 +595,12 @@ providing the '--add_storages 0' parameter. When configuring the storage
configuration manually, keep in mind that the 'data-pool' parameter needs to be
set. Only then will the EC pool be used to store the data objects. For example:
+NOTE: The optional parameters '--size', '--min_size' and '--crush_rule' will be
+used for the replicated metadata pool, but not for the erasure coded data pool.
+If you need to change the 'min_size' on the data pool, you can do it later.
+The 'size' and 'crush_rule' parameters cannot be changed on erasure coded
+pools.
+
[source,bash]
----
pvesm add rbd <storage name> --pool <replicated pool> --data-pool <ec pool>
--
2.30.2
next prev parent reply other threads:[~2022-05-03 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:58 [pve-devel] [PATCH manager/docs 0/3] EC follow ups Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 1/3] ceph pools create: remove crush_rule for ec pool data Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 2/3] ceph pools create: enhance erasure-code description Aaron Lauterer
2022-05-03 11:58 ` Aaron Lauterer [this message]
2022-05-04 5:56 ` [pve-devel] applied: [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation Thomas Lamprecht
2022-05-04 5:56 ` [pve-devel] applied-series: [PATCH manager/docs 0/3] EC follow ups Thomas Lamprecht
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=20220503115809.2566406-4-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal