From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] ceph ec: fix typos and reword some sections
Date: Mon, 27 Jun 2022 15:16:30 +0200 [thread overview]
Message-ID: <20220627131630.3700972-1-a.lauterer@proxmox.com> (raw)
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
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 <pool-name> --erasure-coding profile=<profile-name>
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
next reply other threads:[~2022-06-27 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:16 Aaron Lauterer [this message]
2022-06-28 14:06 ` [pve-devel] applied: " 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=20220627131630.3700972-1-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