From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <a.lauterer@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 49475C4FE for <pve-devel@lists.proxmox.com>; Tue, 3 May 2022 13:58:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3CEA1156B for <pve-devel@lists.proxmox.com>; Tue, 3 May 2022 13:58:11 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 29FBF1547 for <pve-devel@lists.proxmox.com>; Tue, 3 May 2022 13:58:10 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id EF9FA4310D for <pve-devel@lists.proxmox.com>; Tue, 3 May 2022 13:58:09 +0200 (CEST) From: Aaron Lauterer <a.lauterer@proxmox.com> To: pve-devel@lists.proxmox.com Date: Tue, 3 May 2022 13:58:09 +0200 Message-Id: <20220503115809.2566406-4-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220503115809.2566406-1-a.lauterer@proxmox.com> References: <20220503115809.2566406-1-a.lauterer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.005 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Tue, 03 May 2022 11:58:41 -0000 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