From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 23AFB78507 for ; Mon, 27 Jun 2022 15:16:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1F946DA7 for ; Mon, 27 Jun 2022 15:16:32 +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 898BED95 for ; Mon, 27 Jun 2022 15:16:31 +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 5D022436B4 for ; Mon, 27 Jun 2022 15:16:31 +0200 (CEST) From: Aaron Lauterer To: pve-devel@lists.proxmox.com Date: Mon, 27 Jun 2022 15:16:30 +0200 Message-Id: <20220627131630.3700972-1-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.018 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] ceph ec: fix typos and reword some sections X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2022 13:16:32 -0000 Signed-off-by: Aaron Lauterer --- pveceph.adoc | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/pveceph.adoc b/pveceph.adoc index 737f13b..54fb214 100644 --- a/pveceph.adoc +++ b/pveceph.adoc @@ -556,7 +556,7 @@ to recover from a certain amount of data loss. Erasure coded pools can offer more usable space compared to replicated pools, but they do that for the price of performance. -For comparision: in classic, replicated pools, multiple replicas of the data +For comparison: in classic, replicated pools, multiple replicas of the data are stored (`size`) while in erasure coded pool, data is split into `k` data chunks with additional `m` coding (checking) chunks. Those coding chunks can be used to recreate data should data chunks be missing. @@ -567,9 +567,9 @@ losing any data. The total amount of objects stored is `k + m`. Creating EC Pools ^^^^^^^^^^^^^^^^^ -You can create erasuce coded (EC) through using the `pveceph` CLI tooling. As -EC code work different than replicated pools, planning a setup and the pool -parameters used needs to adapt. +Erasure coded (EC) pools can be created with the `pveceph` CLI tooling. +Planning an EC pool needs to account for the fact, that they work differently +than replicated pools. The default `min_size` of an EC pool depends on the `m` parameter. If `m = 1`, the `min_size` of the EC pool will be `k`. The `min_size` will be `k + 1` if @@ -627,9 +627,8 @@ pveceph pool create --erasure-coding profile= Adding EC Pools as Storage ^^^^^^^^^^^^^^^^^^^^^^^^^^ -You can also add an already existing EC pool as storage to {pve}, it works the -same as adding any `RBD` pool but requires to pass the extra `data-pool` -option. +You can add an already existing EC pool as storage to {pve}. It works the same +way as adding an `RBD` pool but requires the extra `data-pool` option. [source,bash] ---- -- 2.30.2